Re: Mapping of timestamptz to TIMESTAMP vs. TIMESTAMP_WITH_TIMEZONE

From: Dave Cramer <davecramer(at)postgres(dot)rocks>
To: Ben Horowitz <bhorowit(at)gmail(dot)com>
Cc: pgsql-jdbc(at)lists(dot)postgresql(dot)org
Subject: Re: Mapping of timestamptz to TIMESTAMP vs. TIMESTAMP_WITH_TIMEZONE
Date: 2023-11-20 15:19:19
Message-ID: CADK3HHKbd=V3+DMvMfvPB4zuTb87mjmc4+GWqQANO7S1LyNY_A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Probably should be. Care to provide a Pull Request ?
Dave Cramer
www.postgres.rocks

On Fri, 17 Nov 2023 at 20:19, Ben Horowitz <bhorowit(at)gmail(dot)com> wrote:

> Hi,
>
> Apologies if this is a duplicate of an answered question. I searched in
> the mailing list archives, Stack Overflow, etc., and didn't find anything.
>
> At the line linked below in TypeInfoCache, it appears that
> type timestamptz is getting mapped to the type java.sql.Types.TIMESTAMP [1]
> . It seems like it should be mapped to
> java.sql.Types.TIMESTAMP_WITH_TIMEZONE.
>
> TIMESTAMP_WITH_TIMEZONE was introduced in Java 8 (2014). Is the mapping of
> timestamptz to TIMESTAMP intentional for reasons of backwards compatibility?
>
> I found the behavior surprising, and also found a question on Stack
> Overflow where someone else was surprised [2].
>
> Thanks very much,
> Ben
>
> [1]
> https://github.com/pgjdbc/pgjdbc/blob/65f158ed8e06ffea77ca7f3b8413847817a7831f/pgjdbc/src/main/java/org/postgresql/jdbc/TypeInfoCache.java#L106
>
> [2]
> https://stackoverflow.com/questions/60451102/for-postgresql-resultsetmetadata-getcolumntype-function-returns-same-value-ty
>

In response to

Browse pgsql-jdbc by date

  From Date Subject
Next Message Nikolay Prokofiev 2023-11-21 09:07:30 Pg jdbc DNS failover
Previous Message Ben Horowitz 2023-11-18 01:19:26 Mapping of timestamptz to TIMESTAMP vs. TIMESTAMP_WITH_TIMEZONE