Skip site navigation (1) Skip section navigation (2)

Re: PREPARE and transactions

From: James Robinson <jlrobins(at)socialserve(dot)com>
To: "Jeroen T(dot) Vermeulen" <jtv(at)xs4all(dot)nl>
Cc: Merlin Moncure <merlin(dot)moncure(at)rcsonline(dot)com>,Richard Huxton <dev(at)archonet(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>,pgsql-hackers(at)postgresql(dot)org
Subject: Re: PREPARE and transactions
Date: 2004-06-24 15:03:33
Message-ID: A93A5E4E-C5EF-11D8-8247-000A9566A412@socialserve.com (view raw or flat)
Thread:
Lists: pgsql-hackers
[ all snipped ]

A problem with redefining the lifetime of a PREPARE'd statement 
according to if it was defined within an explicitly managed transaction 
or not would be with middlewares such as J2EE / EJB containers. The 
container / JDBC driver performs most operations within explicitly 
managed transactions *by the middleware container*, and, if the 
middleware container is configured to cache prepared statements between 
transactions, then it will expect them to live well beyond their 
initial explicitly-managed transaction.

----
James Robinson
Socialserve.com


In response to

pgsql-hackers by date

Next:From: Cyril VELTERDate: 2004-06-24 15:11:48
Subject: [Re] Re: PREPARE and transactions
Previous:From: Dave CramerDate: 2004-06-24 15:02:04
Subject: Re: JDBC prepared statements: actually not server

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group