Re: Can't execute statements with DBD::Oracle

I'd start by adding the argument { RaiseError => 1, PrintError => 0 } to the call to connect. It says it hasn't executed the statement, so it stands to reason it returned an error you didn't check. The above will cause subsequent errors to thrown an exception.

Comment on Re: Can't execute statements with DBD::Oracle Select or Download Code

Replies are listed 'Best First'.
Re^2: Can't execute statements with DBD::Oracle by aremaref (Initiate) on Jun 15, 2009 at 18:42 UTC
Okay, I just tried that, and now instead of printing it nonstop it just prints the same error once, followed by an uninformative "1", then exits. Not sure what to make of that.	[reply]
Re^3: Can't execute statements with DBD::Oracle by ikegami (Patriarch) on Jun 15, 2009 at 18:49 UTC
No idea, and I don't see how that "1" is possible. How can the program print anything after it exited? (A print in the destructor of an object that gets destroyed during global destruction could do it, but you think DBI's objects wouldn't do that.)	[reply]