Re: time stops within transaction

At 12:39 PM 10/18/00 -0400, Tom Lane wrote:
>Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
>> Tom Lane writes:
>>> 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
>
>So? It also says that the choice of exactly when to evaluate now()
>is implementation-dependent.

Note the phrase "during the execution of the SQL-STATEMENT" above. It
says that exactly when it will be evaluated within the statement is
implementation-defined, BUT THAT IT IS EVALUATED WITHIN THE STATEMENT,
not beforehand.

At least, that's how I read it :)

- Don Baccus, Portland OR <dhogaza(at)pacifier(dot)com>
Nature photos, on-line guides, Pacific Northwest
Rare Bird Alert Service and other goodies at
http://donb.photo.net.