Re: PQsendQueryParams() causes prepared statement error - Mailing list pgsql-bugs

From Denis Feklushkin
Subject Re: PQsendQueryParams() causes prepared statement error
Date
Msg-id 1352307845.27348.16.camel@localhost
Whole thread Raw
In response to Re: PQsendQueryParams() causes prepared statement error  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
В Срд, 07/11/2012 в 11:48 -0500, Tom Lane пишет:
> Denis Feklushkin <denis.feklushkin@gmail.com> writes:
> > in 9.2.0:
> > PQsendQueryParams() with multiple command statement (like "select 123;
> > select 456") unexpectedly causes error:
>
> > "cannot insert multiple commands into a prepared statement."
>
> This is not a bug, it's intentional (and documented) behavior.

Advise as I can override this? I am need a simple form of overlapped
processing, as in manual: "the client can be handling the results of one
command while the server is still working on later queries in the same
command string."

pgsql-bugs by date:

Previous
From: Craig Ringer
Date:
Subject: Re: duplicate key value violates unique constraint "tableName_pk"
Next
From: sergey@booksys.com
Date:
Subject: BUG #7641: ERROR: must specify relation and object name when function contains DROP TRIGGER