Re: I was spoiled by the MySQL timestamp field

From: Andrew Sullivan <andrew(at)libertyrms(dot)info>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: I was spoiled by the MySQL timestamp field
Date: 2003-01-27 23:09:26
Message-ID: 20030127180926.A9007@mail.libertyrms.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sun, Jan 26, 2003 at 05:00:36PM -0500, Tom Lane wrote:
> "Matthew Nuzum" <cobalt(at)bearfruit(dot)org> writes:
> > The difference is when now() gets interpreted into a date. Someone
> > please correct me if I'm wrong...

> now() is a function call and will not be folded into a constant.

I know it's not really related, but I think it might be worth noting
here, also, that now() is (was? I don't have anything later than 7.2
handy for testing at the moment) resolves to the beginning of the
transaction. If you need time to move forward during your
transaction, you need timeofday().

A

--
----
Andrew Sullivan 204-4141 Yonge Street
Liberty RMS Toronto, Ontario Canada
<andrew(at)libertyrms(dot)info> M2P 2A8
+1 416 646 3304 x110

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Andrew Sullivan 2003-01-27 23:12:28 Re: pg_xlog safety
Previous Message Curt Sampson 2003-01-27 22:54:34 Re: ORDER BY 'criteria'