Skip site navigation (1) Skip section navigation (2)

Re: [GENERAL] schema error upgrading from 7.1 to 7.2

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Vivek Khera <khera(at)kcilink(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org, pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] schema error upgrading from 7.1 to 7.2
Date: 2002-02-20 21:31:27
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugspgsql-general
Vivek Khera <khera(at)kcilink(dot)com> writes:
>  "owner_lastbilled" date DEFAULT 'CURRENT_DATE' NOT NULL,

The above was never correct.  I believe that 7.1's rather lax date
parser might have interpreted the literal as being 'current'.  7.2's
date parser would reject it, even if 'current' were still an allowed
value, which it is not.

On the other hand, invoking the function CURRENT_DATE

	"owner_lastbilled" date DEFAULT CURRENT_DATE NOT NULL,

was and remains valid.

> This is not documented in the list of changes to the Schema
> Manipulation.

Because it is not one: it is a datatype behavioral change.

			regards, tom lane

In response to


pgsql-bugs by date

Next:From: Vivek KheraDate: 2002-02-20 21:41:51
Subject: Re: [GENERAL] schema error upgrading from 7.1 to 7.2
Previous:From: pgsql-bugsDate: 2002-02-20 21:29:59
Subject: Bug #598: optimizer: convert 'IN' to join

pgsql-general by date

Next:From: Joe ConwayDate: 2002-02-20 21:36:55
Subject: Re: documention on psql?
Previous:From: Charles AlbrechtDate: 2002-02-20 21:28:36
Subject: Re: Ordering 'A', 'B', ..., 'Z', 'AA', 'AB', ...

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group