How could DBI or MySQL even know whether the affected tables are transaction based? What if you mixed them up in your transaction?

 $dbh->do( "INSERT INTO nontrans VALUES ( 'hi' )" );
 $dbh->do( "UPDATE trans SET name = 'hey' WHERE id = 4" );
 $dbh->commit;

[download]

How could either MySQL or DBI deal with this? It's probably a good idea to create two separate connections: one for transactions, one for non-transactions. And is it a good idea to even mix transaction and non-transactional tables in a database? This seems ripe for mistakes to me... but I haven't used transactions in MySQL before, so maybe this is recommended behavior?

Chris
M-x auto-bs-mode

In reply to Re: Apache::DBI , Transactions and Warnings ... Oh my! by lachoy
in thread Apache::DBI , Transactions and Warnings ... Oh my! by BMaximus

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.