| From: | Denis Feklushkin <denis(dot)feklushkin(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: PQsendQueryParams() causes prepared statement error |
| Date: | 2012-11-07 17:04:05 |
| Message-ID: | 1352307845.27348.16.camel@localhost |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
В Срд, 07/11/2012 в 11:48 -0500, Tom Lane пишет:
> Denis Feklushkin <denis(dot)feklushkin(at)gmail(dot)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."
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavan Deolasee | 2012-11-07 17:21:03 | Re: duplicate key value violates unique constraint "tableName_pk" |
| Previous Message | Tom Lane | 2012-11-07 16:48:54 | Re: PQsendQueryParams() causes prepared statement error |