| From: | Dave Cramer <davecramer(at)postgres(dot)rocks> |
|---|---|
| To: | postgresql(at)bergeon(dot)org, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #17911: Database or JDBC Driver Provides Incorrect Type |
| Date: | 2023-05-16 11:43:12 |
| Message-ID: | CADK3HHLrcck+oa_-axwR6GY5pLy9bTZku-mzrEdP3SvJMg-O6g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Hi,
Can you provide more detail please? Possibly are reproducer?
Dave Cramer
www.postgres.rocks
On Thu, 27 Apr 2023 at 14:27, PG Bug reporting form <noreply(at)postgresql(dot)org>
wrote:
> The following bug has been logged on the website:
>
> Bug reference: 17911
> Logged by: Stephen Bergeon
> Email address: postgresql(at)bergeon(dot)org
> PostgreSQL version: 15.2
> Operating system: Windows 10
> Description:
>
> When the JDBC driver returns a ResultSet, both from obtaining table column
> info, as well as from an actual query, the DATA_TYPE returned is incorrect
> for Time-with-Time-Zone and Timestamp-With-Time-Zone columns. In both cases
> the returned value returned indicates that the non-time-zone value is
> returned.
>
> This has been tested on multiple versions of PostgreSQL and its JDBC
> driver through the latest release [database version 15.2 and JDBC driver
> 42.6.0].
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2023-05-16 13:00:00 | BUG #17935: Incorrect memory access in fuzzystrmatch/difference() |
| Previous Message | Sergiu Ignat | 2023-05-16 10:02:20 | XML element with special characters can be created, serialized, but not deserialized |