From: | Jeremy Morton <admin(at)game-point(dot)net> |
---|---|
To: | Andreas Karlsson <andreas(at)proxel(dot)se>, Jeremy Morton <postgres(at)game-point(dot)net>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Support for DATETIMEOFFSET |
Date: | 2020-04-10 13:19:09 |
Message-ID: | e843e98e-b73e-eb92-140b-f4282f6745e7@game-point.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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 opinion. It should be used universally instead of
datetime.
--
Best 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
>> all over the place in TSQL databases.
>
> Hi,
>
> I do not think anyone is working on such a type. And personally I
> think such a type is better suite for an extension rather than for
> core PostgreSQL. For most applications the timestamptz and date types
> are enough to solve everything time related (with some use of the
> timestamp type when doing calculations), but there are niche
> applications where other temporal types can be very useful, but I
> personally do not think those are common enough for inclusion in core
> PostgreSQL.
>
> I suggest writing an extension with this type and see if there is any
> interest in it.
>
> Andreas
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Justin Pryzby | 2020-04-10 13:35:32 | Re: Vacuum o/p with (full 1, parallel 0) option throwing an error |
Previous Message | James Coleman | 2020-04-10 13:18:38 | Re: Multiple FPI_FOR_HINT for the same block during killing btree index items |