Re: [GENERAL] Date & Time

From: <kaiq(at)realtyideas(dot)com>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: "Ross J(dot) Reedstrom" <reedstrm(at)wallace(dot)ece(dot)rice(dot)edu>, Dale Anderson <danderso(at)crystalsugar(dot)com>, pgsql-general(at)postgreSQL(dot)org
Subject: Re: [GENERAL] Date & Time
Date: 1999-12-01 15:33:04
Message-ID: Pine.LNX.4.10.9912010922160.28473-100000@picasso.realtyideas.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

now is a constant, while now() is a function. so, to me,
it should be always now unless you really need now().
what's more, in my impression, now() is not in any official
doc, it is like a rescue for now. however, in this case,
seems there is not much difference.-- oops

as for current_timestamp: I bet it is cos the sql92 thing.
now and now() is not sql92 standard. but not sure if now
or now() are the underlying thing, not sure even whether now
and now() are from the same code. Anybody ideas?

On Tue, 30 Nov 1999, Bruce Momjian wrote:

> > "now" performs better in this case:
> > insert into test values (123, 'now','Name');
> >
> > now() is needed for "default" in create table, because
> > "now" won't work right (a bug/feature ?).
> >
>
> Why does 'now' preform better than now()?
>
> --
> Bruce Momjian | http://www.op.net/~candle
> maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
> + If your life is a hard drive, | 830 Blythe Avenue
> + Christ can be your backup. | Drexel Hill, Pennsylvania 19026
>
> ************
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Ed Loehr 1999-12-01 15:35:21 Re: [GENERAL] "FATAL 1: my bits moved right off the end of theworld!"
Previous Message Massimo Pichini 1999-12-01 14:58:49 postgres libpq library