pgjdbc/pgjdbc GitHub issues and pull requests (mirror)
help / color / mirror / Atom feedFrom: michalkoza (@michalkoza) <[email protected]>
To: pgjdbc/pgjdbc <[email protected]>
Subject: Re: [pgjdbc/pgjdbc] issue #1325: Additional jsr 310 support
Date: Mon, 28 Jul 2025 09:27:15 +0000
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
@vlsi Thanks for reading my input!
I should not have said:
> michalkoza: Instant is a moment in time in UTC.
It is not accurate - it is just default `.toString()` behaviour on this type.
This part of the article represents my point of view: https://wiki.postgresql.org/wiki/Don%27t_Do_This#When_should_you.3F_8
I think that by choosing `Instant` in the app, and `TIMESTAMP` in DB - I'm clearly saying:
"Dear database, I handle time zones on the app side. You do not have to worry about it at all"
Which I think is a super legit approach :) It is hard for me to imagine scenario in which it would be confusing or ambiguous.
... But I have to admit that learning this:
> timestamptz records a single moment in time. Despite what the name says it doesn't store a timestamp, just a point in time described as the number of microseconds since January 1st, 2000 in UTC
does convince me that `Instant` -> `TIMESTAMPZ` is NOT a bad idea :)
view thread (25+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: github://pgjdbc/pgjdbc
Cc: [email protected], [email protected]
Subject: Re: [pgjdbc/pgjdbc] issue #1325: Additional jsr 310 support
In-Reply-To: <<[email protected]>>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox