From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
---|---|
To: | Nicholas E(dot) Wakefield <nwakefield(at)KineticNetworks(dot)com> |
Cc: | <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: Unexpected Statement Caching with CURRENT_TIMESTAMP |
Date: | 2006-08-11 01:05:28 |
Message-ID: | 07452E37-B94D-42E2-89E7-97D4C7446700@fastcrypt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Nicholas,
Yes this is expected behaviour. The time is the time when you started
the transaction. It has nothing to do with JDBC.
Dave
On 10-Aug-06, at 8:37 PM, Nicholas E. Wakefield wrote:
> I'm executing 'SELECT CURRENT_TIMESTAMP' from a statement object with
> auto commit off and prepare threshold set to 1. I'm finding that the
> result comes back the same for after multiple calls and instantiations
> of the statement object(The same happens for a prepared statement).
> However this does not occur when I perform a commit before or after
> every call.
>
> Is this expected behaviour?
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 6: explain analyze is your friend
>
From | Date | Subject | |
---|---|---|---|
Next Message | Oliver Jowett | 2006-08-11 02:03:56 | Re: SQL query never ends |
Previous Message | Nicholas E. Wakefield | 2006-08-11 00:37:30 | Unexpected Statement Caching with CURRENT_TIMESTAMP |