You can do it by subclassing DBI - possible, but not easy.
You can then let all your code do all the commits that they want to, without it affecting the DB, by overloading the commit method in DBI::db::commit as a noop (just a return :) Probably you should log where the commits are called from, to be able to ferret them out of the code later.
Rollback could be extended with errortraceback if neccesary.
At the end you could do a 'real' commit to commit transactions before disconnecting.

Hmmm.........
It is normally a Good Thing (tm) to have short transactions.
Nested transactions are often a sign of design failures.

I would be very cautious with code that forced me to do things like those you describe.

In reply to Re: commtting db transactions by htoug
in thread commtting db transactions by d_i_r_t_y

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.