From: Tom Lane <tgl@sss.pgh.pa.us>
To: Mike Wes <mikeewes@gmail.com>
cc: pgsql-sql@postgresql.org
Subject: Re: Problem wil TIMEZONE vs TIME ZONE
In-reply-to: 
 <CAPLgiTOV3CaBRsBjW_uY+T52qb6kEqW29AL85wFhSC3HHuMh7g@mail.gmail.com>
References: 
 <CAPLgiTOV3CaBRsBjW_uY+T52qb6kEqW29AL85wFhSC3HHuMh7g@mail.gmail.com>
Comments: In-reply-to Mike Wes <mikeewes@gmail.com>
	message dated "Wed, 08 Feb 2017 12:20:35 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1470.1486569158.1@sss.pgh.pa.us>
Date: Wed, 08 Feb 2017 10:52:38 -0500
Message-ID: <1471.1486569158@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-sql-owner@postgresql.org

Mike Wes <mikeewes@gmail.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


-- 
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql