Bruce Momjian wrote:
> It is not clear to me; is this its own transaction or a function call?
That looks like an anonymous PL/SQL procedure to me. Another
question might be, given:
"more than one reference to one or more <datetime value
function>s, then all such references are effectively evaluated
under what conditions does Oracle report *the same* value for
CURRENT_TIMESTAMP? So far, in this discussion, we have the
1. RDBMS start: No one
2. Session start: No one
3. Transaction start: PostgreSQL
4. Statement start: ???
5. CURRENT_TIMESTAMP evaluation: Oracle 9, ???
Given what Tom has posted regarding the standard, I think Oracle
is wrong. I'm wondering how the others handle multiple
references in CURRENT_TIMESTAMP in a single stored
procedure/function invocation. It seems to me that the lower
bound is #4, not #5, and the upper bound is implementation
dependent. Therefore PostgreSQL is in compliance, but its
compliance is not very popular.
> Dan Langille wrote:
>> time1 TIMESTAMP;
>> time2 TIMESTAMP;
>> sleeptime NUMBER;
>> sleeptime := 5;
>> SELECT CURRENT_TIMESTAMP INTO time1 FROM DUAL;
>> SELECT CURRENT_TIMESTAMP INTO time2 FROM DUAL;
>>30-SEP-02 11.54.09.583576 AM
>>30-SEP-02 126.96.36.1998333 AM
>>PL/SQL procedure successfully completed.
In response to
pgsql-hackers by date
|Next:||From: Peter Eisentraut||Date: 2002-09-30 20:07:24|
|Subject: Re: Do we want a CVS branch now? |
|Previous:||From: Bruce Momjian||Date: 2002-09-30 19:07:27|
|Subject: Re: (Fwd) Re: Any Oracle 9 users? A test please...|