Re: [SQL] AutoCommit and DDL

2005-02-28 Thread Andrew - Supernews
On 2005-03-01, Don Drake <[EMAIL PROTECTED]> wrote: > I don't think it would be easy to duplicate since our code base is > quite extensive. > > Basically, what was happening was a script would first open a database > connection (AutoCommit turned off by default), create a few objects > (that also o

Re: [SQL] AutoCommit and DDL

2005-02-28 Thread Don Drake
I don't think it would be easy to duplicate since our code base is quite extensive. Basically, what was happening was a script would first open a database connection (AutoCommit turned off by default), create a few objects (that also opened independent db connections), the objects would run querie

Re: [SQL] AutoCommit and DDL

2005-02-28 Thread Michael Fuhr
On Sun, Feb 27, 2005 at 07:55:35PM -0600, Don Drake wrote: > The problem has to do with multiple concurrent connections to the > server causing problems. I've removed the concurrent connections and > now this works. Strange. Can you elaborate? Can you describe the scenario with enough detail t

Re: [SQL] AutoCommit and DDL

2005-02-28 Thread Michael Fuhr
On Sun, Feb 27, 2005 at 11:55:37AM -0600, Don Drake wrote: > 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. Have you used any of DBI's tracing capabilities? Could you post a simple test case? The fo

Re: [SQL] AutoCommit and DDL

2005-02-27 Thread Don Drake
I did some traces and it all looks OK. The problem has to do with multiple concurrent connections to the server causing problems. I've removed the concurrent connections and now this works. Strange. -Don On Sun, 27 Feb 2005 12:54:34 -0700, Michael Fuhr <[EMAIL PROTECTED]> wrote: > On Sun, Feb

Re: [SQL] AutoCommit and DDL

2005-02-27 Thread Don Drake
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 <[EMAIL PROTECTED]> wrote: > On Sat, Feb 26, 2005 at 02:56:52PM -0600, Don Drake wrote: > > > I turned

Re: [SQL] AutoCommit and DDL

2005-02-26 Thread Michael Fuhr
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

[SQL] AutoCommit and DDL

2005-02-26 Thread Don Drake
I have a generic function that creates partition tables and their corresponding indexes and constraints. I've tested the function using a GUI and it works great. We implemented in our data loaders (written in perl) and the DB connections have AutoCommit turned off. When we run it in the perl scr

Re: [SQL] autocommit

2004-03-26 Thread Tom Lane
Kemin Zhou <[EMAIL PROTECTED]> writes: > Could we add one simple switch to psql (the client front end or the > library) --noautocommit? psql already has this, see \set AUTOCOMMIT. regards, tom lane ---(end of broadcast)---

[SQL] autocommit

2004-03-26 Thread Kemin Zhou
This might be a wish list or add feature. Could we add one simple switch to psql (the client front end or the library) --noautocommit? This will require you to type commit at the end of a query. Most of the time I would be using psql to do simple stuff. Some times I need to update databases.