On 3 November 2012 00:45, geeky2 <gee...@hotmail.com> wrote: [...] > > we are thinking of doing this to represent a 1:M relationship with the > "Many" being represented as a string in the schema (probably comprised > either of xml or json objects). > > we are looking at the classic part : model scenario, where the client would > look up a part and the document would contain a string field with > potentially 200+ model numbers. edge cases for this could be 400+ model > numbers. >
Why would you want to do this over having a multi-valued field for the model number? Regards, Gora
