Although I can't say how/why dbsqlexec is overriding your 'die' handler, you might be able to use an alternative: 
$SIG{'__DIE__'} = \&my_die_handler;

[download]
Unless another package changes this setting, this traps anyone's call to 'die'.
Update: I think I misunderstood what you were saying you did.

Once you install a new handler for '__DIE__' (or __WARN__), then even 'die's or 'warn's inside of evals will call your code. The handler catches all instances of these calls within the scope of that %SIG modification. One solution to this is to reset the handlers inside the eval block: 
eval {
  local $SIG{'__DIE__'} = 'DEFAULT';
  $dbh->nsql;
}

[download]

In reply to Re: Overriding CORE::GLOBAL::die and $^S by saintly
in thread Overriding CORE::GLOBAL::die and $^S by aufflick

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.