Re: I was spoiled by the MySQL timestamp field

From: Lincoln Yeoh <lyeoh(at)pop(dot)jaring(dot)my>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Matthew Nuzum" <cobalt(at)bearfruit(dot)org>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: I was spoiled by the MySQL timestamp field
Date: 2003-01-27 04:09:43
Message-ID: 5.1.0.14.1.20030127120417.02849070@mbox.jaring.my
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

At 05:00 PM 1/26/03 -0500, Tom Lane wrote:
>(BTW, the reason 'now' without "timestamp" in front works is that this
>is not a timestamp literal but a text literal, which will be coerced
>to timestamp at runtime.)

Is it known at the moment which of those methods the Postgresql team are
aiming to continue supporting for the near/medium future?

e.g. current_timestamp is guaranteed. now() for the forseeable future.
'now' for the next few versions.

Thanks,
Link.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2003-01-27 04:20:52 Re: I was spoiled by the MySQL timestamp field
Previous Message Bruno Wolff III 2003-01-27 03:31:42 Re: getting weekly total based on daily...