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

From: Francisco Olarte <folarte(at)peoplecall(dot)com>
To: Eduardo Pérez Ureta <edpeur(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, "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-04 11:06:58
Message-ID: CA+bJJbxJ0ZivkQGCwXR8w=it+CmMEcQDkRG11ECwHhs4x91n+g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Eduardo:

On Tue, Oct 3, 2017 at 11: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.

Are you sure they ( other DB ) do it this way? I've not used too many
other databases recently, but what I remember is they deviated from
the standard not because it was broken, but because it was easier to
deviate than not.

Francisco Olarte.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Sean Chittenden 2017-10-04 17:47:06 Re: [PATCH] BUG #13416: Postgres =?utf-8?Q?>=3D_?=9.3 doesn't use optimized shared memory on Solaris anymore
Previous Message Andres Freund 2017-10-04 01:38:56 Re: [BUGS] BUG #14825: enum type: unsafe use?