Uhhh... Should have thought of that. Thanks for pointing it out. :-) Hmmm... Doesn't make much sense to have a function to lock tables then because it either needs to turn off AutoCommit upon entering the function (in which case you have unseen side effects ) or assume it has been turned off (in which case it silently fails to work). I guess what I should do is check to see if it is off and warn if not ...
> -----Original Message----- > From: Michael A Chase [mailto:[EMAIL PROTECTED]] > Sent: Thursday, June 06, 2002 5:39 PM > To: Tim Harsch; [EMAIL PROTECTED] > Subject: Re: Locks in DBD::Oracle > > > On Thu, 6 Jun 2002 14:53:42 -0700 Tim Harsch <[EMAIL PROTECTED]> wrote: > > > I'm having trouble with obtaining locks on tables with a > DBI script. I > > have the following function which has been run at the beginning of a > > long running script. However, after starting the script I > am able to go > > into sqlplus and obtain exclusive locks on the tables in question. > > > > I'm sure it has to do with the persistence of the statement > handle or > > something... > > Have you turned off AutoCommit? > -- > Mac :}) > ** I normally forward private questions to the appropriate > mail list. ** > Ask Smarter: http://www.tuxedo.org/~esr/faqs/smart-questions.html > Give a hobbit a fish and he eats fish for a day. > Give a hobbit a ring and he eats fish for an age. > > >
