Re: BUG #14842: TIMESTAMP WITH TIME ZONE and TIMESTAMP WITHOUT TIMEZONE should not be comparable

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Eduardo Pérez Ureta <edpeur(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #14842: TIMESTAMP WITH TIME ZONE and TIMESTAMP WITHOUT TIMEZONE should not be comparable
Date: 2017-10-03 21:54:34
Message-ID: CAKFQuwZPmXux++yVkN312cGKfZst1kqFMEjQLjGQb0wj6GwFRQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Oct 3, 2017 at 2:19 PM, Eduardo Pérez Ureta <edpeur(at)gmail(dot)com>
wrote:

> I did not know that the SQL standard was so broken. Maybe it is time to
> consider only following the SQL standard in its non-broken parts, like
> other SQL databases do.
>

​It has its quirks but the two you have fixated on seem easy enough to
avoid.

At this point we've already decided that being conforming is generally a
virtue; especially since I'd assume that at least some "other SQL
databases" also conform to these same rules. Deciding to become more
strict (as opposed to starting out that way) requires significant benefit.

​David J.​

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message John R Pierce 2017-10-03 22:00:47 Re: BUG #14842: TIMESTAMP WITH TIME ZONE and TIMESTAMP WITHOUT TIMEZONE should not be comparable
Previous Message David G. Johnston 2017-10-03 21:42:57 Re: BUG #14841: Remove TIME WITH TIME ZONE type