I guess it won't work for Transaction. not tested though. (need
to put the program sleep a while). I just use
'current_timestamp(now)'::datetime in the program (yes, read off now or just
get
time from perl should also work. current_timestamp just save a little
perl coding). Not really tested. I trust the documentation :-)
seems to me very complicated to implement (so, not likely happening)
that you can use current_timestamp WITHIN the create table statement
(just like using now()) to make time uniform through a transaction.
maybe I should test after I finish this project. I need to FINISH it TODAY
;-)
>From: Charles Tassell <ctassell@isn.net>
>To: pgsql-general@postgreSQL.org
>Subject: Re: [GENERAL] current_timestamp and default now()
>Date: Tue, 26 Oct 1999 11:19:32 -0300
>
>I believe it works if you put now() in single quotes. EG:
>
>create table test (
> proposetime datetime not null default 'now()',
>)
>
>
>At 10:07 PM 10/25/99, Lincoln Yeoh wrote:
>>At 01:05 PM 25-10-1999 PDT, amy cheng wrote:
>> >hi, there,
>> >
>> >I'm using:
>> >
>> >create table test (
>> >proposetime datetime not null default now(),
>> >)
>> >
>> >then, I find that I need to make the time uniform through the
>> >transaction. Is there a way to use current_timestamp('now')
>> >in the create table statement? Seems impossible?
>>
>>How about reading off the current time (select <somethingblahblah> 'now',
>>I
>>can't remember how to do it- not very obvious at first sight) and then
>>using that time throughout the transaction?
>>
>>Cheerio,
>>
>>Link.
>>
>>
>>************
>
>
>************
>
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
