| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: 7.4 compatibility question |
| Date: | 2003-10-22 04:21:34 |
| Message-ID: | 8468.1066796494@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers |
Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> writes:
>>> Now that DEFAULT 'now' will not work in PostgreSQL 7.4, will DEFAULT
>>> 'infinity' and DEFAULT '-infinity' and the like stop working as well?
>>
>> No, because those values don't change over time. The issue here is when
>> exactly does the default value get evaluated...
> Ah, of course - but what about 'yesterday' and 'tomorrow' - these should
> also be mentioned in the release notes.
Good point ... not that I think anyone is actually using such a default
in the field, but the behavior did change ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2003-10-22 04:31:33 | Re: 7.4 compatibility question |
| Previous Message | Christopher Kings-Lynne | 2003-10-22 04:18:59 | Re: 7.4 compatibility question |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2003-10-22 04:31:33 | Re: 7.4 compatibility question |
| Previous Message | Christopher Kings-Lynne | 2003-10-22 04:18:59 | Re: 7.4 compatibility question |