From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | edpeur(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-03 20:38:43 |
Message-ID: | 30437.1507063123@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> On Tue, Oct 3, 2017 at 12:52 PM, <edpeur(at)gmail(dot)com> wrote:
>> Currently you can do:
>> CREATE TABLE t1 (ts TIMESTAMP WITH TIME ZONE NOT NULL,tr TIMESTAMP WITHOUT
>> TIME ZONE NOT NULL);
>> INSERT INTO t1 (ts,tr) VALUES (CURRENT_TIMESTAMP, CURRENT_TIMESTAMP);
>> SELECT * FROM t1 WHERE ts=tr;
>>
>> But it should fail with:
>> ERROR: operator does not exist: timestamp with time zone = timestamp
>> without time zone
>> Also CURRENT_TIMESTAMP should fail to be inserted into a TIMESTAMP WITHOUT
>> TIME ZONE column
>> ERROR: column "tr" is of type timestamp without time zone but expression
>> is of type timestamp with time zone
> This is working as intended and given the amount of pain removing implicit
> casts generally involves it is unlikely to change.
Not to mention that the SQL standard requires these implicit casts to
exist.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Eduardo Pérez Ureta | 2017-10-03 21:19:17 | Re: BUG #14841: Remove TIME WITH TIME ZONE type |
Previous Message | David G. Johnston | 2017-10-03 20:20:40 | Re: BUG #14842: TIMESTAMP WITH TIME ZONE and TIMESTAMP WITHOUT TIMEZONE should not be comparable |