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 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-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.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-02-20 23:18:13 | Re: [GENERAL] schema error upgrading from 7.1 to 7.2 |
Previous Message | Tom Lane | 2002-02-20 21:31:27 | Re: [GENERAL] schema error upgrading from 7.1 to 7.2 |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2002-02-20 21:47:09 | Re: Ordering 'A', 'B', ..., 'Z', 'AA', 'AB', ... |
Previous Message | Glen Parker | 2002-02-20 21:40:26 | Re: Alternate database locations |