I see your point and I agree. In order to keep things simple lets always create a resultset.
>>> [log in to unmask] 14-06-02 15:16 >>>
> I agree with Mike, although when a server does not support position
> based resultsets the client can not do anything about it.
I agree with Mike too, for what it's worth.
> We don't need an extra parameter: when the client asks for 0 records
> there will be no resultset in all other cases there will be, so we do
That's not strictly correct. I could not want to be returned any records,
but still want a result set.
I want to do some operation on two result sets. I search for them,
requesting 0 records in response. Then do the operation on the
resultsets, and ask for 10 records in response. Rather than just
discarding the records from the first two searches, it should be possible
to have a result set created when 0 records are requested.
,'/:. Rob Sanderson ([log in to unmask])
,'--/::(@)::. Special Collections and Archives, extension 3142
,'---/::::::::::. Twin Cathedrals: telnet: liverpool.o-r-g.org 7777
____/:::::::::::::. WWW: http://liverpool.o-r-g.org:8000/
I L L U M I N A T I