From: Greg Speegle <Greg@10happythings.com>
To: Peter Mount <petermount@maidstone.gov.uk>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: JDBC Drop/Create problem?
Date: Thu, 07 Dec 2000 12:19:12 -0600
Message-ID: <3A2FD4A0.7030000@10happythings.com> (raw)
References: <1B3D5E532D18D311861A00600865478CF1B635@exchange1.nt.maidstone.gov.uk>
Ah. That explains it. Thanks.
Out of curiosity, why does the transaction get marked as aborted? I
only ask since others
(e.g. Oracle) don't have this behavior.
Greg
Peter Mount wrote:
> Dropping a non-existent table should throw an exception as well as mark any
> open transaction as aborted.
>
> I'd say either:
>
> * using autoCommit while checking for existing tables.
> * commit and begin a new transaction afterwards.
> * Use temporary tables, so the table doesn't survive the connection.
>
> Peter
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: Greg@10happythings.com, petermount@maidstone.gov.uk
Subject: Re: JDBC Drop/Create problem?
In-Reply-To: <3A2FD4A0.7030000@10happythings.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox