| From: | Jeremy Morton <admin(at)game-point(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jeremy Morton <postgres(at)game-point(dot)net> |
| Cc: | Andreas Karlsson <andreas(at)proxel(dot)se>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Support for DATETIMEOFFSET |
| Date: | 2020-04-17 13:36:03 |
| Message-ID: | 6d8f7fc6-41a4-aa16-7099-30b74eadef74@game-point.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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 <postgres(at)game-point(dot)net> 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 is pretty popular)
>> right now, using "the world's most advanced open source relational
>> database", is reason enough to support it?
>
> If the ORM somehow prevents you from using timestamptz, that's a
> bug in the ORM. If it doesn't, the above is just a hysterical
> claim with no factual foundation.
>
> regards, tom lane
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2020-04-17 13:50:56 | Re: While restoring -getting error if dump contain sql statements generated from generated.sql file |
| Previous Message | Jehan-Guillaume de Rorthais | 2020-04-17 13:33:04 | Re: [BUG] non archived WAL removed during production crash recovery |