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
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
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
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
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
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
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
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
