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

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

From: Vivek Khera <khera(at)kcilink(dot)com>
To: 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:41:51
Message-ID: 15476.6175.283661.944402@onceler.kciLink.com (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-general
>>>>> "TL" == Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:

TL> Vivek Khera <khera(at)kcilink(dot)com> writes:
>> "owner_lastbilled" date DEFAULT 'CURRENT_DATE' NOT NULL,

TL> The above was never correct.  I believe that 7.1's rather lax date
TL> parser might have interpreted the literal as being 'current'.  7.2's

Then how come pg_dump outputs it that way?  Is it because that's how I
did it when creating the schema in the first place?

I guess I extended putting the quotes around that because of the
warnings about putting quotes around 'NOW()' as a default.  My
mistake...

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

It isn't documented in the HISTORY file in any way shape or form.
Where else should I look for potential traps in validating my app
under 7.2?

Thanks.


In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2002-02-20 23:18:13
Subject: Re: [GENERAL] schema error upgrading from 7.1 to 7.2
Previous:From: Tom LaneDate: 2002-02-20 21:31:27
Subject: Re: [GENERAL] schema error upgrading from 7.1 to 7.2

pgsql-general by date

Next:From: Bruce MomjianDate: 2002-02-20 21:47:09
Subject: Re: Ordering 'A', 'B', ..., 'Z', 'AA', 'AB', ...
Previous:From: Glen ParkerDate: 2002-02-20 21:40:26
Subject: Re: Alternate database locations

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