RE: JDBC Drop/Create problem?

--
Peter Mount
Enterprise Support Officer, Maidstone Borough Council
Email: petermount(at)maidstone(dot)gov(dot)uk
WWW: http://www.maidstone.gov.uk
All views expressed within this email are not the views of Maidstone Borough
Council

> -----Original Message-----
> From: Joachim Achtzehnter [mailto:joachim(at)kraut(dot)ca]
> Sent: Friday, December 08, 2000 6:27 PM
> To: pgsql-interfaces(at)postgresql(dot)org
> Subject: RE: [INTERFACES] JDBC Drop/Create problem?
>
>
> Today, in a message to Greg Speegle, Peter Mount wrote:

> > What would be nice would be nested transactions. Then the drop could
> > be placed within its own transaction, and the outer one wouldn't be
> > affected.
>
> Nested transactions are more general than statement-level
> abort in that
> they allow users to define the scope of the nested
> transaction. It is also
> the preferred way to cleanly implement statement-level abort.

The problem JDBC has is that it's DatabaseMetaData methods can make several
queries. While AutoCommit is off, if one of those fails, the users
transaction will also fail. Could be a possible area of confusion for both
user and app.

Peter