Re: Anomalies with the now() function

From: David Roussel <diroussel(at)xsmail(dot)com>
To: Byrne Kevin-kbyrne01 <kbyrne01(at)motorola(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Anomalies with the now() function
Date: 2005-11-19 15:43:56
Message-ID: 8E62D326-D0D9-4863-9D56-C811DDF6818A@xsmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I don't know about this particular problem, but I find in programming
in general it's always best to pass in the value of now as a
parameter, and pass it on to functions you are calling, thus avoiding
problems with mismatching values.

But as Andreas says the values should be the same within the same
transaction, at least that's what I thought.

David

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Ezra Taylor 2005-11-19 16:07:55 Re: Sun supporting PostgreSQL
Previous Message David Roussel 2005-11-19 15:36:59 Re: shorter way to get new value of serial?