| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Fuhr <mike(at)fuhr(dot)org> |
| Cc: | Oliver Elphick <olly(at)lfix(dot)co(dot)uk>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Problem with COPY in 8.0.3 |
| Date: | 2005-10-12 21:48:08 |
| Message-ID: | 4415.1129153688@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Michael Fuhr <mike(at)fuhr(dot)org> writes:
> On Wed, Oct 12, 2005 at 08:23:15PM +0100, Oliver Elphick wrote:
>> I actually use CURRENT_DATE; that is what the system turns it into.
> Ah yes, I see that now. I generally use now(), so I hadn't noticed
> that CURRENT_DATE and CURRENT_TIMESTAMP become 'now', whereas only
> a literal 'now' is expanded at create time:
Yeah. That implementation of CURRENT_TIMESTAMP and friends is
historical, and probably ought to be changed sometime. It works OK
but it's ugly, especially for reverse-listing purposes.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oliver Elphick | 2005-10-12 22:34:12 | Re: Problem with COPY in 8.0.3 |
| Previous Message | Tom Lane | 2005-10-12 21:45:17 | Re: Problem with COPY in 8.0.3 |