>> anyField (any field in the underlying data, indexed or not)
>> anyKnown (any field indexed, not necessarily in CQL)
>> anyIndex (any field with a CQL Index == current cql.anywhere)
> Do we still need server-choice? I'd always interpreted the different
Yes, IMO. As below.
> between this and anywhere/anyIndex to be that anywhere would search all
> indexes whereas serverchoice would search only one index (somehow
> appropriately or inappropriate chosen by the server).
Right. It should probably be:
allFields
allKnown
allIndexes (Indices?)
> Personally I'd like to see it go - I don't want any indeterminate "and
> the server will do the appropriate thing" in SRW ;-)
Then you need to map some index and relation to the CQL query: "fish"
Or to the query: "2005-01-07"
Different databases should have the facility to handle these queries
differently, because the user is explicitly giving control of the query to
the server (by not including the index)
Secondly, just because we may (or may not) want indeterminate queries in
SRW, doesn't mean that CQL shouldn't be allowed to support them.
Rob
,'/:. Dr Robert Sanderson ([log in to unmask])
,'-/::::. http://www.o-r-g.org/~azaroth/
,'--/::(@)::. Dept. of Computer Science, Room 805
,'---/::::::::::. University of Liverpool
____/:::::::::::::. L5R Shop: http://www.cardsnotwords.com/
I L L U M I N A T I
|