Skip site navigation (1) Skip section navigation (2)

Re: Clarify use of NOW() in pl/pgsql docs

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Neil Conway <neilc(at)samurai(dot)com>
Cc: Michael Glaesemann <grzm(at)myrealbox(dot)com>,David Fetter <david(at)fetter(dot)org>,PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: Clarify use of NOW() in pl/pgsql docs
Date: 2005-02-11 00:36:44
Message-ID: 4742.1108082204@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-patches
Neil Conway <neilc(at)samurai(dot)com> writes:
> On Thu, 2005-02-10 at 16:32 +0900, Michael Glaesemann wrote:
>> I realize it's a bit late, but it might not be a bad idea to use 
>> CURRENT_TIMESTAMP rather than NOW(), as it's per SQL spec.

> I can't say I can get very excited about it; someone is free to submit a
> patch if they like.

Considering that the example in question is embedded in the 100%-not-SQL-
standard language plpgsql, I can't get excited about this either.

			regards, tom lane

In response to

Responses

pgsql-patches by date

Next:From: Neil ConwayDate: 2005-02-11 01:26:59
Subject: reject empty string in float[48], oid
Previous:From: Neil ConwayDate: 2005-02-11 00:36:00
Subject: Re: WIP: pl/pgsql cleanup

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group