Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #56180 > unrolled thread
| Started by | "F.R." <anthra.norell@bluewin.ch> |
|---|---|
| First post | 2013-10-05 10:39 +0200 |
| Last post | 2013-10-05 10:39 +0200 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Where does MySQLdb put inserted data? "F.R." <anthra.norell@bluewin.ch> - 2013-10-05 10:39 +0200
| From | "F.R." <anthra.norell@bluewin.ch> |
|---|---|
| Date | 2013-10-05 10:39 +0200 |
| Subject | Re: Where does MySQLdb put inserted data? |
| Message-ID | <mailman.741.1380971999.18130.python-list@python.org> |
On 10/05/2013 12:55 AM, Dennis Lee Bieber wrote: > On Fri, 04 Oct 2013 09:38:41 +0200, "F.R." <anthra.norell@bluewin.ch> > declaimed the following: > > <snip convoluted unformatted stuff> > > MySQLdb, as with all DB-API compliant adapters, does NOT do > "auto-commit" -- you MUST execute a con.commit() after any query (sequence) > that modifies data. Without it, closing the connection will invoke a > ROLLBACK operation, removing any attempted changes. That's it! It works! Thank you sooo much. A miracle how I could go without commits for years and never have missing data. Anyway, another lesson learned . . . Thanks Frederic
Back to top | Article view | comp.lang.python
csiph-web