X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 7C891565CF for ; Sun, 27 Feb 2005 04:21:02 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 12871-06 for ; Sun, 27 Feb 2005 04:20:52 +0000 (GMT) Received: from tigger.fuhr.org (tigger.fuhr.org [63.214.45.158]) by svr1.postgresql.org (Postfix) with ESMTP id E18B5565BA for ; Sun, 27 Feb 2005 04:20:50 +0000 (GMT) Received: from winnie.fuhr.org (winnie.fuhr.org [10.1.0.1]) by tigger.fuhr.org (8.13.1/8.13.1) with ESMTP id j1R4KiWf044049 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sat, 26 Feb 2005 21:20:46 -0700 (MST) (envelope-from mfuhr@winnie.fuhr.org) Received: from winnie.fuhr.org (localhost [127.0.0.1]) by winnie.fuhr.org (8.13.1/8.13.1) with ESMTP id j1R4KhAM077506; Sat, 26 Feb 2005 21:20:43 -0700 (MST) (envelope-from mfuhr@winnie.fuhr.org) Received: (from mfuhr@localhost) by winnie.fuhr.org (8.13.1/8.13.1/Submit) id j1R4KhXT077505; Sat, 26 Feb 2005 21:20:43 -0700 (MST) (envelope-from mfuhr) Date: Sat, 26 Feb 2005 21:20:43 -0700 From: Michael Fuhr To: Don Drake Cc: pgsql-sql@postgresql.org Subject: Re: AutoCommit and DDL Message-ID: <20050227042043.GB77382@winnie.fuhr.org> References: <6c21003b050226125634e9964@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6c21003b050226125634e9964@mail.gmail.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.003 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200502/333 X-Sequence-Number: 20443 On Sat, Feb 26, 2005 at 02:56:52PM -0600, Don Drake wrote: > I turned AutoCommit on and re-ran the perl script and the tables get > created. Why won't these table's get created when AutoCommit is off? > Why do I have to commit DDL? If you're using DBI, are you using PrintError or RaiseError or otherwise checking the success of each command? My first guess would be that some command is failing (e.g., a DROP of an object that doesn't exist), so the transaction is automatically rolled back even though you requested a commit. -- Michael Fuhr http://www.fuhr.org/~mfuhr/