Re: Unexpected sorting results when sorting with mutivalued filed

2009-04-07 Thread Chris Hostetter
: > The last value is used for sorting in multi-valued fields. What is the : > reason behind sorting on a multi-valued field? strictly speaking the behavior is non-determinisitic. in most cases attempting to sort on a multi-valued field will generate an error. : Cant do much about it, that is

Re: Unexpected sorting results when sorting with mutivalued filed

2009-04-01 Thread tushar kapoor
in the results. >> > > The last value is used for sorting in multi-valued fields. What is the > reason behind sorting on a multi-valued field? > > -- > Regards, > Shalin Shekhar Mangar. > > Cant do much about it, that is the way our design is. Is there any way

Re: Unexpected sorting results when sorting with mutivalued filed

2009-03-31 Thread Shalin Shekhar Mangar
On Tue, Mar 31, 2009 at 2:18 PM, tushar kapoor < tushar_kapoor...@rediffmail.com> wrote: > > I have indexes with a multivalued field authorLastName. I query them with > sort=authorLastName asc and get the results as - > > Index# authorLastName > 1 Antonakos > 2 Keller > 3

Unexpected sorting results when sorting with mutivalued filed

2009-03-31 Thread tushar kapoor
(Antonakos ) .. Should'nt Index#3 preceed Index#2 in the results. If this is not the default behaviour, what is the right work around for it. Regards, Tushar. -- View this message in context: http://www.nabble.com/Unexpected-sorting-results-when-sorting-with-mutivalued-filed-tp22800877p228