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@game-point.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
>