Tom Lane writes: > Peter Eisentraut <[EMAIL PROTECTED]> writes: > > Tom Lane writes: > >> That is what now() is defined to return: transaction start time. > > > Then CURRENT_TIMESTAMP is in violation of SQL. > > Au contraire, if it did not behave that way it would violate the spec. > See SQL92 6.8 general rule 3: > > 3) If an SQL-statement generally contains more than one reference > to one or more <datetime value function>s, then all such ref- > erences are effectively evaluated simultaneously. The time of > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > evaluation of the <datetime value function> during the execution > of the SQL-statement is implementation-dependent. statement != transaction -- Peter Eisentraut [EMAIL PROTECTED] http://yi.org/peter-e/
- [HACKERS] time stops within transaction Alex Pilosov
- Re: [HACKERS] time stops within transaction Bruce Momjian
- Re: [HACKERS] time stops within transaction John Huttley
- Re: [HACKERS] time stops within transaction Tom Lane
- Re: [HACKERS] time stops within transaction Peter Eisentraut
- Re: [HACKERS] time stops within transaction Tom Lane
- Re: [HACKERS] time stops within transact... Peter Eisentraut
- Re: [HACKERS] time stops within tra... Tom Lane
- Re: [HACKERS] time stops within... Peter Eisentraut
- Re: [HACKERS] time stops within... Don Baccus
- Re: [HACKERS] time stops within... Alex Pilosov
- Re: [HACKERS] time stops wi... Tom Lane
- Re: [HACKERS] time stops wi... Hiroshi Inoue
- Re: [HACKERS] time stops wi... Tom Lane
- Re: [HACKERS] time stops wi... Hiroshi Inoue
- Re: [HACKERS] time stops wi... Vadim Mikheev
- Re: [HACKERS] time stops wi... Hiroshi Inoue