Re: [GENERAL] CURRENT_TIMESTAMP
От | Ross J. Reedstrom |
---|---|
Тема | Re: [GENERAL] CURRENT_TIMESTAMP |
Дата | |
Msg-id | 20020924151003.GC7612@rice.edu обсуждение исходный текст |
Ответ на | Re: [GENERAL] CURRENT_TIMESTAMP (Roland Roberts <roland@astrofoto.org>) |
Ответы |
Re: [GENERAL] CURRENT_TIMESTAMP
|
Список | pgsql-sql |
On Tue, Sep 24, 2002 at 10:55:41AM -0400, Roland Roberts wrote: > >>>>> "Martijn" == Martijn van Oosterhout <kleptog@svana.org> writes: > > Martijn> Well, what I would suggest is that when you wrap several > Martijn> statements into a single transaction with begin/commit, > Martijn> the whole lot could be considered a single statement > Martijn> (since they form an atomic transaction so in a sense they > Martijn> are all executed simultaneously). And hence Postgresql is > Martijn> perfectly compliant. > > FWIW, and not that I am an Oracle fan :-), Oracle seems to interpret > this the same way when using a "select sysdate from dual" inside a > transaction. Oh, interesting datapoint. Let me get this clear - on oracle, the equivalent of: BEGIN; SELECT current_timestamp; <go off to lunch, come back> SELECT current_timestamp; END; will give two identical timestamps? Ross
В списке pgsql-sql по дате отправления: