Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>If you are using ubuntu Linux there was a patch added to the python-mysql package that added the ability to set that same MYSQL_OPT_RECONNECT option (see <a href="https://launchpad.net/ubuntu/hardy/+source/python-mysqldb/1.2.2-5" rel="noreferrer">here</a>). I have not tried it though.</p> <p>Unfortunately, the patch was later removed due to a conflict with autoconnect and transations (described <a href="https://launchpad.net/ubuntu/+source/python-mysqldb" rel="noreferrer">here</a>).</p> <p>The comments from that page say: 1.2.2-7 Published in intrepid-release on 2008-06-19 </p> <p>python-mysqldb (1.2.2-7) unstable; urgency=low</p> <p>[ Sandro Tosi ] * debian/control - list items lines in description starts with 2 space, to avoid reformat on webpages (Closes: #480341)</p> <p>[ Bernd Zeimetz ] * debian/patches/02_reconnect.dpatch: - Dropping patch: Comment in Storm which explains the problem:</p> <pre><code> # Here is another sad story about bad transactional behavior. MySQL # offers a feature to automatically reconnect dropped connections. # What sounds like a dream, is actually a nightmare for anyone who # is dealing with transactions. When a reconnection happens, the # currently running transaction is transparently rolled back, and # everything that was being done is lost, without notice. Not only # that, but the connection may be put back in AUTOCOMMIT mode, even # when that's not the default MySQLdb behavior. The MySQL developers # quickly understood that this is a terrible idea, and removed the # behavior in MySQL 5.0.3. Unfortunately, Debian and Ubuntu still # have a patch right now which *reenables* that behavior by default # even past version 5.0.3. </code></pre>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload