multiValued fields retain their order, for the record.

        Erik


On Sep 4, 2007, at 12:37 AM, Jed Reynolds wrote:
One of the difficulties that you're going to find with multi-valued fields is that they are an unordered collection without relation. If you have a document with a list of editors and revisions, the two fields have no inherent correlation unless your application can extract it from the data itself.

[doc]
   [id]123[/id]
   [str name=name]hello world[/str]
   [array name=editor]
       [str name=editor]Fred[/str]
       [str name=editor]Bob[/str]
   [/array]
   [array name=revisiondate]
      [date name=revisiondate]2006-01-01T00:00:00Z[/date]
      [date name=revisiondate]2006-01-02T00:00:00Z[/date]
   [/array]
[/doc]

If your application can decipher that and do a slice on it showing a revision...then brilliant! But if the multi-value fields are out of order, that might make a significant different.

I would create a document per revision and take advantage of range queries and sorting available at the query level.




Jed

Reply via email to