Not sure what you consider a rumor, I just simply stated having a problem
with it before and that in my experience I always check for return value,
due to either the query failing and/or executing without failing, but still
producing an unexpected result.
By implying that the trasaction does not fail without checking for return,
does not necessarily mean that there was an SQL error, but rather the query
produced an unexpected result.
Sorry if I offended you in any way, since you decided to flame me, without
reading the whole thread.
Ilya Sterin
-----Original Message-----
From: [EMAIL PROTECTED]
To: Sterin, Ilya
Cc: Stephen Clouse; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: 05/06/2001 10:47 PM
Subject: Re: executing atomic transactions in DBI
>>>>> "Sterin," == Sterin, Ilya <[EMAIL PROTECTED]> writes:
Sterin> There is no || die anywhere in that eval? Even with
Sterin> RaiseError => 1 turned on, in many cases the transaction does
Sterin> not fail, if not checking for some sort of return.
I think this is FUD. My understanding is that RaiseError = 1
completely eliminates the need for || die on any DBI call. If you
have examples to the contrary, please post them -- don't just rumor
about them.
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777
0095
<[EMAIL PROTECTED]> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl
training!
