| From: | Thomas Lockhart <lockhart(at)fourpalms(dot)org> |
|---|---|
| To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: text -> time cast problem |
| Date: | 2001-12-10 05:03:07 |
| Message-ID: | 3C14420B.FDAA9D4@fourpalms.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
...
> Is there anything wrong with any of these behaviours, and has any of it been
> changed for 7.2? I kind think that the quoted CURRENT_TIMESTAMP should work
> just like the unquoted...
No, it is pretty much the same as before. Quoted 'current_timestamp' has
nothing to do with the SQL9x standard, while unquoted CURRENT_TIMESTAMP
does. For 7.2, we are dropping the somewhat interesting 'current' value,
which was evaluated at the time a math operation was performed, at which
time it became equivalent to 'now'.
- Thomas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hiroshi Inoue | 2001-12-10 07:38:57 | Re: Bug #533: BLOB (lo type) objects could not be restored |
| Previous Message | Thomas Lockhart | 2001-12-10 04:59:07 | Minor updates for date/time committed |