Received: from thor.tht.net (thor.tht.net [209.47.145.4])
	by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id eB7Ia7P87287
	for <pgsql-interfaces@postgresql.org>;
	Thu, 7 Dec 2000 13:36:07 -0500 (EST)
	(envelope-from Greg@10happythings.com)
Received: from waco2.calpha.com (root@waco2.calpha.com [208.232.233.3])
	by thor.tht.net (8.9.3/8.9.3) with ESMTP id OAA92913
	for <pgsql-interfaces@postgresql.org>; Thu, 7 Dec 2000 14:19:37 GMT
	(envelope-from Greg@10happythings.com)
Received: from 10happythings.com (gspeegle.t1-s.wireless.calpha.com
	[63.80.26.25] (may be forged))
	by waco2.calpha.com (8.10.1/8.10.1) with ESMTP id eB7IJEV24454;
	Thu, 7 Dec 2000 12:19:15 -0600
Message-ID: <3A2FD4A0.7030000@10happythings.com>
Date: Thu, 07 Dec 2000 12:19:12 -0600
From: Greg Speegle <Greg@10happythings.com>
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US;
	m18) Gecko/20001108 Netscape6/6.0
X-Accept-Language: en
MIME-Version: 1.0
To: Peter Mount <petermount@maidstone.gov.uk>
CC: pgsql-interfaces@postgresql.org
Subject: Re: JDBC Drop/Create problem?
References: 
 <1B3D5E532D18D311861A00600865478CF1B635@exchange1.nt.maidstone.gov.uk>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Archive-Number: 200012/54
X-Sequence-Number: 391


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
>