[Xesam] Sorting API to be more flexible

[Mikkel Kamstrup Erlandsen]

2008/6/29 Arun Raghavan <arunisgod at gmail.com>:
> On Sun, Jun 29, 2008 at 7:52 PM, Mikkel Kamstrup Erlandsen
> <mikkel.kamstrup at gmail.com> wrote:
> [...]
>> I think we have agreement on this. I have put it on the list of
>> pending changes for the next release (be that 1.0 or RC3):
>> http://xesam.org/main/XesamUpdates
>>
>> So if nobody starts complaining this one will go in. Speak now or
>> forever hold your silence :-)
>
> One question -- shouldn't the sort.order field now be a list of
> strings of the length of sort.fields? I think this makes things a
> little uglier, but is probably necessary.

To be honest I didn't even think about that. I think that this may be
tricky to implement on some backends, I will have to check up on
sqlite, Lucene, and Xapian to verify this. I am also wondering about
the real usefulness of this feature. Do we have some concrete use
cases? Urho's original Artist, Album, Track# does not seem to require
this feature at least. Will think.

Cheers,
Mikkel