MIME-Version: 1.0
References: 
 <CAM1tkGVCRayeakBXb7ZqDTuJRFup7_kiF1S4gc8-_b99Cy0i-A@mail.gmail.com>
In-Reply-To: 
 <CAM1tkGVCRayeakBXb7ZqDTuJRFup7_kiF1S4gc8-_b99Cy0i-A@mail.gmail.com>
From: Dave Cramer <davecramer@postgres.rocks>
Date: Mon, 20 Nov 2023 10:19:19 -0500
Message-ID: 
 <CADK3HHKbd=V3+DMvMfvPB4zuTb87mjmc4+GWqQANO7S1LyNY_A@mail.gmail.com>
Subject: Re: Mapping of timestamptz to TIMESTAMP vs. TIMESTAMP_WITH_TIMEZONE
To: Ben Horowitz <bhorowit@gmail.com>
Cc: pgsql-jdbc@lists.postgresql.org
Content-Type: multipart/alternative; boundary="0000000000008769d9060a97033e"
Archived-At: 
 <https://www.postgresql.org/message-id/CADK3HHKbd%3DV3%2BDMvMfvPB4zuTb87mjmc4%2BGWqQANO7S1LyNY_A%40mail.gmail.com>
Precedence: bulk

--0000000000008769d9060a97033e
Content-Type: text/plain; charset="UTF-8"

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@gmail.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
>

--0000000000008769d9060a97033e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Probably should be. Care to provide a Pull Request ?<br cl=
ear=3D"all"><div><div dir=3D"ltr" class=3D"gmail_signature" data-smartmail=
=3D"gmail_signature"><div dir=3D"ltr">Dave Cramer<div>www.postgres.rocks</d=
iv></div></div></div><br></div><br><div class=3D"gmail_quote"><div dir=3D"l=
tr" class=3D"gmail_attr">On Fri, 17 Nov 2023 at 20:19, Ben Horowitz &lt;<a =
href=3D"mailto:bhorowit@gmail.com">bhorowit@gmail.com</a>&gt; wrote:<br></d=
iv><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bord=
er-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div>=
Hi,</div><div><br></div><div>Apologies if this is a duplicate of an answere=
d question. I searched in the mailing list archives, Stack Overflow, etc., =
and didn&#39;t find anything.</div><div><br></div>At the line linked below =
in TypeInfoCache, it appears that type=C2=A0timestamptz is getting mapped t=
o the type java.sql.Types.TIMESTAMP [1] . It seems like it should be mapped=
 to java.sql.Types.TIMESTAMP_WITH_TIMEZONE.<div><br></div><div>TIMESTAMP_WI=
TH_TIMEZONE was introduced in Java 8 (2014). Is the mapping of timestamptz =
to TIMESTAMP intentional for reasons of backwards compatibility?</div><div>=
<br></div><div>I found the behavior surprising, and also found a question o=
n Stack Overflow where someone else was surprised [2].</div><div><br></div>=
<div>Thanks very much,</div><div>Ben</div><div><br></div><div>[1]=C2=A0<a h=
ref=3D"https://github.com/pgjdbc/pgjdbc/blob/65f158ed8e06ffea77ca7f3b841384=
7817a7831f/pgjdbc/src/main/java/org/postgresql/jdbc/TypeInfoCache.java#L106=
" target=3D"_blank">https://github.com/pgjdbc/pgjdbc/blob/65f158ed8e06ffea7=
7ca7f3b8413847817a7831f/pgjdbc/src/main/java/org/postgresql/jdbc/TypeInfoCa=
che.java#L106</a></div><div><br></div><div>[2] <a href=3D"https://stackover=
flow.com/questions/60451102/for-postgresql-resultsetmetadata-getcolumntype-=
function-returns-same-value-ty" target=3D"_blank">https://stackoverflow.com=
/questions/60451102/for-postgresql-resultsetmetadata-getcolumntype-function=
-returns-same-value-ty</a><br></div></div>
</blockquote></div>

--0000000000008769d9060a97033e--