| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Thomas Lockhart <lockhart(at)fourpalms(dot)org> |
| Cc: | Nicolas Paymal <npaymal(at)instranet(dot)com>, <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: CURRENT_TIMESTAMP not work correctly insinde a transaction. |
| Date: | 2002-02-22 22:04:44 |
| Message-ID: | Pine.LNX.4.30.0202221702050.686-100000@peter.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Thomas Lockhart writes:
> > In a transaction until you commit your transaction through a jdbc
> > connection, each time you use the Current_timestamp (or 'now'), the
> > timestamps is always the same, and when your transaction is very long you
> > have undesirable effect.
>
> This is not a bug, but the behavior required by SQL9x afaicr.
AFAIK, this is PostgreSQL bugward compatibility. SQL says that
current_timestamp returns the "current timestamp", which you can interpret
any way you want to.
--
Peter Eisentraut peter_e(at)gmx(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Coax | 2002-02-22 22:47:11 | Possible bug concerning LASTOID in 7.2 |
| Previous Message | Thomas Lockhart | 2002-02-22 18:42:38 | Re: CURRENT_TIMESTAMP not work correctly insinde a transaction. |