| From: | chap(at)anastigmatix(dot)net |
|---|---|
| To: | Dave Cramer <davecramer(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: CommandStatus from insert returning when using a portal. |
| Date: | 2023-07-14 16:07:53 |
| Message-ID: | 0100cc45a5fb70ad689ff5dbafd9ef3a@anastigmatix.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2023-07-12 20:57, Dave Cramer wrote:
> Without a cursor it returns right away as all of the results are
> returned
> by the server. However with cursor you have to wait until you fetch the
> rows before you can get the CommandComplete message which btw is wrong
> as
> it returns INSERT 0 0 instead of INSERT 2 0
To make sure I am following, was this describing a comparison of
two different ways in Java, using JDBC, to perform the same operation,
one of which behaves as desired while the other doesn't? If so, for
my curiosity, what do both ways look like in Java?
Or was it a comparison of two different operations, say one
an INSERT RETURNING and the other something else?
Regards,
-Chap
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Cramer | 2023-07-14 16:29:57 | Re: CommandStatus from insert returning when using a portal. |
| Previous Message | Tom Lane | 2023-07-14 15:57:09 | Re: Allowing parallel-safe initplans |