From: | Dennis Gearon <gearond(at)cvc(dot)net> |
---|---|
To: | Bruno Wolff III <bruno(at)wolff(dot)to> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: three timestamps/table, use of 'now' in table creation statement |
Date: | 2003-01-16 21:00:44 |
Message-ID: | SRLIQP2V08HQXUI3X82UKJ2WLF65.3e271d7c@cal-lab |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
What would it be rounded to, for the sake of knowledge?
I will change all my table defintions to timestamp(0). BTW, what is the default resolution? I'm am
in the process of RTFM'ing, don't worry.
1/16/2003 12:48:06 PM, Bruno Wolff III <bruno(at)wolff(dot)to> wrote:
>Note you seem to have forgotten to cc the list on this message.
>
>On Thu, Jan 16, 2003 at 09:42:10 -0800,
> Dennis Gearon <gearond(at)cvc(dot)net> wrote:
>> Thank you for all the replies, I now have half of my question answered. What I need to know is
>> what I can put in the table definition for the default value to have the current timestamp put
in
>> the three timestamp fields.
>>
>> 1/ Can I put 'now' as the default value
>> in the table definition?
>>
>> 2/ can I put CURRENT_TIMESTAMP(0) as the default value ...
>> in the table definition?
>
>I believe both of these will work. If the column is of type timestamp
>(as opposed to timestamp(0)) then 'now''s value won't be rounded to
>the nearest second.
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-01-16 21:06:16 | Re: Server error and deadlocks |
Previous Message | Bruno Wolff III | 2003-01-16 20:48:06 | Re: three timestamps/table, use of 'now' in table creation statement |