Tom Lane wrote: > Martijn van Oosterhout <kleptog@svana.org> writes: > > libpq supports it just fine. You do a PQsendQuery() and then as many > > PQgetResult()s as it takes to get back the results. This worked for a > > while AFAIK. > > That only works if the caller is prepared to read each result serially, > and not (say) a row at a time in parallel. There are a bunch of > ease-of-use problems as well, such as knowing which resultset is which, > coping with errors detected after the first resultset(s) are sent, etc. > > A more realistic way of dealing with multiple resultsets is to deliver > them as named cursor references and allow the client to FETCH > reasonable-sized chunks. We can sort of handle this today, but it's > notationally painful at both the stored-procedure and client ends.
Is there a TODO here? -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 1: 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
