What can a user or client do with the information that there are too
many terms matched by asking for cql.anywhere? If I understand it
correctly cql.anywhere doesn't work at all for that specific database,
so I would suggest to Ralph just to not support cql.anywhere for that
database.
Theo

>>> [log in to unmask] 27-8-04 15:16:20 >>>
> No, the problem is that too many terms were generated to be OR'd
together.
> The result set might end up with only one record in it.

Do intermediate stages count as result sets? I guess not.

It's also not that the number of records in the intermediate stage is
too
large (as there could be only one record per term).

Okay, I'm convinced.

130:  Too many terms matched by masked query term ?

With Ralph's example as the note and an unspecified details format?

(As knowing the maximum number of terms that a mask can match is for
all
intents and purposes useless to the client)

Rob

>> cql.serverChoice="gsafd*".  My engine threw an exception saying that
the
>> list of terms generated was too big, but I don't have an SRW
diagnostic to
>> return for that case.

> Surely:
> 60      Result set not created: too many matching records

       ,'/:.          Dr Robert Sanderson ([log in to unmask])
     ,'-/::::.        http://www.o-r-g.org/~azaroth/
   ,'--/::(@)::.      Special Collections and Archives, extension 3142
,'---/::::::::::.    University of Liverpool
____/:::::::::::::.  L5R Shop: http://www.cardsnotwords.com/
I L L U M I N A T I