Re: [GENERAL] CURRENT_TIMESTAMP

Tom,

> I'd be happier with the whole thing if anyone had exhibited a convincing
> use-case for statement timestamp.  So far I've not seen any actual
> examples of situations that are not better served by either transaction
> timestamp or true current time.  And the spec is perfectly clear that
> CURRENT_TIMESTAMP does not mean true current time...

Are we still planning on putting the three different versions of now() on the
TODO?  I.e.,
now('transaction'),
now('statement'), and
now('immediate')
With now() = now('transaction')?

I still think it's a good idea, provided that we have some easy means to
determine now('statement').

--
-Josh Berkus
 Aglio Database Solutions
 San Francisco