Oliver Jowett <[EMAIL PROTECTED]> writes:
Tom Lane wrote:
How can clients distinguish multiple resultsets if they're using the extended query protocol?
You'll get multiple repetitions of RowDescription/DataRows.
Ah, so the Execute spontaneously generates a RowDescription spontaneously when it hits the second resultset, without needing an extra Describe?
Oh, wait, you won't get anything. My example was using simple-Query protocol. In extended Query you get nothing, per this comment in pquery.c:
Ok, thanks. It looks like the driver is doing the right thing then.
Here's a one-line patch that clarifies the Execute protocol docs slightly.
-O
Index: doc/src/sgml/protocol.sgml
===================================================================
RCS file: /projects/cvsroot/pgsql-server/doc/src/sgml/protocol.sgml,v
retrieving revision 1.53
diff -u -c -r1.53 protocol.sgml
*** doc/src/sgml/protocol.sgml 16 Aug 2004 02:12:29 -0000 1.53
--- doc/src/sgml/protocol.sgml 23 Sep 2004 23:02:43 -0000
***************
*** 747,753 ****
The possible
responses to Execute are the same as those described above for queries
issued via simple query protocol, except that Execute doesn't cause
! ReadyForQuery to be issued.
</para>
<para>
--- 747,753 ----
The possible
responses to Execute are the same as those described above for queries
issued via simple query protocol, except that Execute doesn't cause
! ReadyForQuery or RowDescription to be issued.
</para>
<para>
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
