| 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: | 2672.1014240687@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vivek Khera | 2002-02-20 21:41:51 | Re: [GENERAL] schema error upgrading from 7.1 to 7.2 |
| Previous Message | pgsql-bugs | 2002-02-20 21:29:59 | Bug #598: optimizer: convert 'IN' to join |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2002-02-20 21:36:55 | Re: documention on psql? |
| Previous Message | Charles Albrecht | 2002-02-20 21:28:36 | Re: Ordering 'A', 'B', ..., 'Z', 'AA', 'AB', ... |