From: | Don Drake <dondrake(at)gmail(dot)com> |
---|---|
To: | Michael Fuhr <mike(at)fuhr(dot)org> |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: AutoCommit and DDL |
Date: | 2005-02-27 17:55:37 |
Message-ID: | 6c21003b0502270955673432e7@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
I know it's not failing, I have the server logging the commands and
there are no errors.
The only change made was turning AutoCommit on.
-Don
On Sat, 26 Feb 2005 21:20:43 -0700, Michael Fuhr <mike(at)fuhr(dot)org> wrote:
> 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/
>
--
Donald Drake
President
Drake Consulting
http://www.drakeconsult.com/
http://www.MailLaunder.com/
312-560-1574
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Fuhr | 2005-02-27 19:54:34 | Re: AutoCommit and DDL |
Previous Message | Mike Rylander | 2005-02-27 17:43:23 | Re: Serial and Index |