From: | Randall Perry <rgp(at)systame(dot)com> |
---|---|
To: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Date/time value 'current' no longer available |
Date: | 2002-04-27 21:48:06 |
Message-ID: | B8F094D6.13DBD%rgp@systame.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thanks
> Randall Perry <rgp(at)systame(dot)com> writes:
>> I'm upgrading to 7.2 and saw this in the FAQ. Does this mean any value with
>> current at the beginning no longer works -- i.e. current_timestamp?
>
> No, it means the magic value 'current' is no longer available.
> This has nothing to do with any SQL-specified behavior; it was a
> poorly-considered hack that we inherited from Berkeley.
>
>> If not, what's suggested in it's place?
>
> 'now' still works, but doesn't have quite the same behavior ('now' is
> converted to a specific timestamp upon input).
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html
--
Randy Perry
sysTame
Mac Consulting/Sales
phn 772.589.6449
mobile email help(at)systame(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Gould | 2002-04-27 22:24:51 | Re: requesting features in PostgreSQL |
Previous Message | Tom Lane | 2002-04-27 21:41:30 | Re: Date/time value 'current' no longer available |