comment on

Because I have 3 separate update and/or insert statements per do, wanted to make sure all succeed, and wasn't sure exactly how the return value would account for all possible errors. From my testing, it looks like do returns only the last statement result rows.

Now if I add a rollback before the 2nd eval:

warn $inventoryUpdate.$statement."\n";
eval{
  $result=$db->do($inventoryUpdate.$statement);
  warn "result1=$result\n";
};
if($@){
  warn "Can't update.  Trying insert.\n\n$inventoryInsert$statement";
  $db->rollback;
  eval{
    $result=$db->do($inventoryInsert.$statement);
    warn "result1=$result\n";
  };
  if ($@){
    warn "Aborted because $@";
    $db->rollback;
    return 0;
  }
}
$db->commit;
[download]

It works! Apparently, the rollback resets $@, but why is the $@ message different in the 2nd eval without the rollback?

In reply to Re^2: SQL through perl is giving error by ksublondie
in thread SQL through perl is giving error by ksublondie

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Perl-Sensitive Sunglasses
	PerlMonks