| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Clemens Eisserer <linuxhippy(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #16230: Boolean column stick to "false" after calling updateRow() on updateable ResultSet |
| Date: | 2020-01-26 06:56:53 |
| Message-ID: | CAKFQuwaL5xLVx=d0-CEbGZR2Ne7_AMVYLzzpAw5o3nBu9gXc1Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-jdbc |
On Sat, Jan 25, 2020 at 12:06 PM PG Bug reporting form <
noreply(at)postgresql(dot)org> wrote:
> The following bug has been logged on the website:
>
> Bug reference: 16230
> Logged by: Clemens Eisserer
> Email address: linuxhippy(at)gmail(dot)com
> PostgreSQL version: 12.1
> Operating system: linux / platform independent
> Description:
>
> Boolean columns always seem to stick to "false" after updateRow() is called
> on updateable ResultSets (this is a regression and worked with
> PostgreSQL-8.4.21 & postgresql-8.4-701.jdbc3.jar ).
>
The core PostgreSQL team doesn't maintain the pgJDBC driver. You need to
report this to them using their process.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lukáš Sobotka | 2020-01-26 07:00:00 | Segfault on updating foreign table |
| Previous Message | David G. Johnston | 2020-01-26 06:53:58 | Re: SQL/PostgreSQL - Error observed in the QUERY not caught by the “EXCEPTION” block in the stored procedure |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2020-01-26 06:58:48 | Re: Boolean column stick to "false" after calling updateRow() on updateable ResultSet |
| Previous Message | David G. Johnston | 2020-01-26 06:47:52 | Re: BUG #16232: Database server connection limit exceeding |