On 13/2/20 5:58 pm, JohnD Blackburn wrote:
The DBA pulled info from some cache that showed the SQL statement from the
script was executed 12610 times.
So if I were to add an “or die $!” statement after the fetchrow_array(), that might fix things? (or prevent it from trying to continue if
On Feb 13, 2020, at 8:30 AM, Fennell, Brian
mailto:fenne...@radial.com>> wrote:
Try to figure out how you can do the whole thing in a single SQL statement,
then just process the results one row at time.
Well, based on his example code that’s exactly what he was doing. The only loop
was
If you are trying to execute one SQL statement against the database for each
loop iteration – you are doing it wrong.
You are adding a round trip for every row which will be slow for the client and
waist time and other resources on the server.
Look on the net for other approaches using NVL and
Hi John,
in my opinion do yourself a favor and use the RaiseError-option of DBI.
Any error you then get while using DBI related calls raise and exception. And
when
you think about it there a seldom cases where you can react better than
killing a process getting a db related error. And if
