-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/16/07 17:25, Chris Browne wrote:
> [EMAIL PROTECTED] (Vladimir Zelinski) writes:
>> I tried function now(),current_timestamp() but all of
>> them behave similar.
>>
>> I don't believe that it's bug, probably it's a feature
>> of the postgreSql da
The problem with gettimeofday() is that it returns a string, rather than
a timestamp. This was all clarified in 8.2:
Add clock_timestamp(), statement_timestamp(), and
transaction_timestamp() (Bruce)
clock_timestamp() is the current wall-clock time,
statement_timestamp
[EMAIL PROTECTED] (Vladimir Zelinski) writes:
> I tried function now(),current_timestamp() but all of
> them behave similar.
>
> I don't believe that it's bug, probably it's a feature
> of the postgreSql database.
Indeed, that is intentional. CURRENT_TIMESTAMP and NOW() return the
time at which t
Thank you very much.
It works.
Vladimir
--- Alvaro Herrera <[EMAIL PROTECTED]> wrote:
> Vladimir Zelinski wrote:
>
> > I don't believe that it's bug, probably it's a
> feature
> > of the postgreSql database.
>
> Correct.
>
> > Is any way to insert a timestamp within the same
> > transaction
Vladimir Zelinski wrote:
> I don't believe that it's bug, probably it's a feature
> of the postgreSql database.
Correct.
> Is any way to insert a timestamp within the same
> transaction that would have current system time (not
> time of the beginning of the transaction)?
timeofday()
--
Alvaro
