Re: Problem wil TIMEZONE vs TIME ZONE

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Mike Wes <mikeewes(at)gmail(dot)com>
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: Problem wil TIMEZONE vs TIME ZONE
Date: 2017-02-08 15:52:38
Message-ID: 1471.1486569158@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

Mike Wes <mikeewes(at)gmail(dot)com> writes:
> Can anybody clarify the following behaviour of pgsql? A Windows user in our
> project is not able to execute a create table command caused by the
> timestamp field log_created using 'TIME ZONE' (giant_log2), but must
> explict use 'TIMEZONE' (giant_log3). This is an issue while we use
> liquibase in our project. Any ideas why this is happening?

That sounds quite backwards. TIMESTAMP WITH TIME ZONE is the SQL-standard
way of spelling the type name. TIMESTAMP WITH TIMEZONE is not in the
standard and it's not accepted by Postgres either, as you can easily
prove by experiment:

regression=# create table foo(f1 TIMESTAMP WITH TIMEZONE);
ERROR: syntax error at or near "WITH"
LINE 1: create table foo(f1 TIMESTAMP WITH TIMEZONE);
^
regression=# create table foo(f1 TIMESTAMP WITH TIME ZONE);
CREATE TABLE

I think you must've had some confusion as to who issued which
command.

regards, tom lane

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message Herwig Goemans 2017-02-09 16:39:19 function source code not returning from inside a pgsql function.
Previous Message Adrian Klaver 2017-02-08 14:32:39 Re: Problem wil TIMEZONE vs TIME ZONE