On Sun, Nov 20, 2005 at 10:01:24PM +0100, Magnus Hagander wrote: > FWIW, MSSQL used to do only multiple sequential resultsets (from stored > procs, or semicolon separated statements). With SQL 2005, they added > interleaved ones - see > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql90 > /html/MARSinSQL05.asp (loads of details both about how it was before and > how it is in 2005)
I saw that page but my understanding of it is that you are now allowed to submit a new query without reading all the results of the last one. And that subsequent reading of results may be interleaved. What it doesn't do is allow a single query to return multiple results sets in an interleaved order. What I'm trying to say is that the client can't read the results of a function in any other order than it calls RETURN NEXT. OTOH, if the server returns a cursor handle, the client can read the cursors in any order it chooses. Is this clear, or am I just confusing people (including possibly myself)? Have a nice day, -- Martijn van Oosterhout <kleptog@svana.org> http://svana.org/kleptog/ > Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a > tool for doing 5% of the work and then sitting around waiting for someone > else to do the other 95% so you can sue them.
pgpAkRpUiE8jR.pgp
Description: PGP signature
