How could the ORM use timestamptz when that doesn't actually store
both a datetime and an offset?
--
Best regards,
Jeremy Morton (Jez)
Tom Lane wrote:
Jeremy Morton writes:
Surely the fact that you'll lose data if you try to store a common
.NET datatype with any kind of ORM (eg. EF, which
Andreas Karlsson wrote:
On 4/10/20 3:19 PM, Jeremy Morton wrote:
Oh well. Guess I keep using SQL Server then. datetimeoffset makes
it impossible for developers to make the mistake of forgetting to
use UTC instead of local datetime, and for that reason alone it
makes it invaluable in my
Neil wrote:
On Apr 10, 2020, at 8:19 AM, Jeremy Morton wrote:
Oh well. Guess I keep using SQL Server then. datetimeoffset makes it
impossible for developers to make the mistake of forgetting to use UTC instead
of local datetime, and for that reason alone it makes it invaluable in my
regards,
Jeremy Morton (Jez)
Andreas Karlsson wrote:
On 4/10/20 10:34 AM, Jeremy Morton wrote:
I've noticed that Postgres doesn't have support for DATETIMEOFFSET
(or any functional equivalent data type) yet. Is this on the
roadmap to implement? I find it a very useful data type that I use
I've noticed that Postgres doesn't have support for DATETIMEOFFSET (or
any functional equivalent data type) yet. Is this on the roadmap to
implement? I find it a very useful data type that I use all over the
place in TSQL databases.
--
Best regards,
Jeremy Morton (Jez)
