From: | "Mario Weilguni" <mario(dot)weilguni(at)icomedias(dot)com> |
---|---|
To: | "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: (Fwd) Re: Any Oracle 9 users? A test please... |
Date: | 2002-10-03 08:56:10 |
Message-ID: | 4D618F6493CE064A844A5D496733D667039101@freedom.icomedias.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
>
>
>Has anyone done the corresponding experiments on the other DBMSes to
>identify exactly when they allow CURRENT_TIMESTAMP to advance ?
>
This applies up to Oracle 8.1.6, maybe it helps:
According to a co-worker, Oracle advances the time in transactions:
select to_char(sysdate, 'dd.mm.yyyy hh24:mi:ss') from dual;
TO_CHAR(SYSDATE,'DD
-------------------
03.10.2002 10:16:28
(wait ...)
SQL> r
1* select to_char(sysdate, 'dd.mm.yyyy hh24:mi:ss') from dual
TO_CHAR(SYSDATE,'DD
-------------------
03.10.2002 10:17:41
It even advances within procedures/functions, example:
create or replace procedure foobar is
s1 varchar(2000);
s2 varchar(2000);
begin
select to_char(sysdate, 'dd.mm.yyyy hh24:mi:ss') into s1 from dual;
(... put long running query here ...)
select to_char(sysdate, 'dd.mm.yyyy hh24:mi:ss') into s2 from dual;
dbms_output.put_line(s1);
dbms_output.put_line(s2);
end;
/
set serverout on
execute foobar;
Hope it helps.
Regards,
Mario Weilguni
From | Date | Subject | |
---|---|---|---|
Next Message | Nigel J. Andrews | 2002-10-03 09:49:10 | anoncvs and diff |
Previous Message | Mark Kirkwood | 2002-10-03 07:56:47 | Re: (Fwd) Re: Any Oracle 9 users? A test please... |