Re: Bad timestamp external representation - Mailing list pgsql-general

From Mark Tessier
Subject Re: Bad timestamp external representation
Date
Msg-id 20030429133144.47d3eca0.m_tessier@sympatico.ca
Whole thread Raw
In response to Re: Bad timestamp external representation  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On Tue, 29 Apr 2003 00:02:20 -0400
Tom Lane <tgl@sss.pgh.pa.us> wrote:

> Mark Tessier <m_tessier@sympatico.ca> writes:
> > Actually, that was the last thing I tried before I wrote this note. Before I entered
>
> > herboris=> INSERT INTO cart (cartid, clientid, invdate, paydate) VALUES
> > herboris-> (4469858, 2, 'current', 'now');
> > And still got the same error message:
> > ERROR:  Bad date external representation 'current'
>
> 'now' is the only accepted spelling.
>
> ('current' used to mean something subtly different from 'now', but that
> meaning isn't supported anymore.)

I should have mentioned that I'm using version 7.3. As a result of using version 7.3, I'm beginning to realize that my
"PracticalPostgresql" book isn't quite up to date. The reason I want to use current timestamp constant is because it
allowsme to calculate the elapsed time between current and now constants (current - now = elapsed_time_in_days)
Accordingto the book, "If you watch the...row with the current timestamp, you'll notice it changes in each query to
showthe updated system time...".(pg. 81). Anyway, since the "current" meaning isn't supported anymore, how would I go
aboutcalculating the amount of time (in days) that has elapsed since inserting or updating a field with the initial
date.

Thanks for your help,

Mark Tessier


pgsql-general by date:

Previous
From: David Link
Date:
Subject: Re: RESOLUTION: pq_recvbuf: unexpected EOF
Next
From: Robert Treat
Date:
Subject: Re: Inheritence woes