Re: [GENERAL] ODBC Layer and the now() function

2005-12-05 Thread Pandurangan R S
Hi, I hope the following link will help you. http://www.postgresql.org/docs/8.0/static/plpgsql-expressions.htmlOn 12/5/05, Byrne Kevin-kbyrne01 <[EMAIL PROTECTED]> wrote: Has anyone seen any strange behaviour as regards the now() function when accessing a db via odbc layer. The behaviour I have

Re: [GENERAL] ODBC Layer and the now() function

2005-12-05 Thread Tom Lane
Byrne Kevin-kbyrne01 <[EMAIL PROTECTED]> writes: > Moserver receives the event - timestamps it as 't1' > -- time lapse before moserver computes the transaction and gives it to odbc. > Txn_begin- now() gets frozen to 't2' > Insert - now() should put it as 't2' > Txn_end()- done. > So firstly t2 sh

Re: [GENERAL] ODBC Layer and the now() function

2005-12-05 Thread Pandurangan
Hi,the following link might help you.http://www.postgresql.org/docs/8.0/static/plpgsql-expressions.htmlOn 12/5/05, Byrne Kevin-kbyrne01 <[EMAIL PROTECTED]> wrote: Has anyone seen any strange behaviour as regards the now() function when accessing a db via odbc layer. The behavio

[GENERAL] ODBC Layer and the now() function

2005-12-05 Thread Byrne Kevin-kbyrne01
Has anyone seen any strange behaviour as regards the now() function when accessing a db via odbc layer. The behaviour I have seen (which I have mentioned in pervious post) is as follows: I have a trigger set up on a db - when a row is added to a certain table (say Table A) in my db the trigger