*** Tom Lane <[EMAIL PROTECTED]> [Wednesday, 21.February.2001, 16:55 -0500]:
> Hmm, exactly what I was thinking of, except that it returns a text
> rather than a timestamp (a strange choice...).
But it's implicit casted to timestamp type so i think is good choice to
use in DEFAULT clause at this
Daniel Wickstrom <[EMAIL PROTECTED]> writes:
> the timeofday function seems to work:
Hmm, exactly what I was thinking of, except that it returns a text
rather than a timestamp (a strange choice...). It seems a little
buggy as well because the formatting of the microseconds part is
wrong --- will
> "Radoslaw" == Radoslaw Stachowiak <[EMAIL PROTECTED]> writes:
Radoslaw> *** Tom Lane <[EMAIL PROTECTED]> [Tuesday,
Radoslaw> 20.February.2001, 11:57 -0500]:
>> > using now() to init TIMESTAMP fields I got resolution of one
>> second. How > can I define DEFAULT in column (TIM
*** Tom Lane <[EMAIL PROTECTED]> [Tuesday, 20.February.2001, 11:57 -0500]:
> > using now() to init TIMESTAMP fields I got resolution of one second. How
> > can I define DEFAULT in column (TIMESTAMP type) to get higher
> > time-resolution (TIMESTAMP supports microseconds).
>
> You could make a var
Radoslaw Stachowiak <[EMAIL PROTECTED]> writes:
> using now() to init TIMESTAMP fields I got resolution of one second. How
> can I define DEFAULT in column (TIMESTAMP type) to get higher
> time-resolution (TIMESTAMP supports microseconds).
You could make a variant of now() that relies on gettimeo
Hello!
using now() to init TIMESTAMP fields I got resolution of one second. How
can I define DEFAULT in column (TIMESTAMP type) to get higher
time-resolution (TIMESTAMP supports microseconds).
Please CC the answer to me.
--
radoslaw.stachowiak.http://alt
