Unexpected Statement Caching with CURRENT_TIMESTAMP - Mailing list pgsql-jdbc

From Nicholas E. Wakefield
Subject Unexpected Statement Caching with CURRENT_TIMESTAMP
Date
Msg-id 2F2A7EB72EBAF24582513E72ACCBCAAE17D8C9@kniexch01.KineticNetworks.com
Whole thread Raw
In response to Re: SQL query never ends  (Mark Lewis <mark.lewis@mir3.com>)
Responses Re: Unexpected Statement Caching with CURRENT_TIMESTAMP  (Dave Cramer <pg@fastcrypt.com>)
Re: Unexpected Statement Caching with CURRENT_TIMESTAMP  (Markus Schaber <schabi@logix-tt.com>)
List pgsql-jdbc
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?

pgsql-jdbc by date:

Previous
From: Mark Lewis
Date:
Subject: Re: SQL query never ends
Next
From: Dave Cramer
Date:
Subject: Re: Unexpected Statement Caching with CURRENT_TIMESTAMP