Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!newsfeed.xs4all.nl!newsfeed2.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
Return-Path: <awilliam@whitemice.org>
X-Original-To: python-list@python.org
Delivered-To: python-list@mail.python.org
X-Spam-Status: OK 0.004
X-Spam-Evidence: '*H*': 0.99; '*S*': 0.00; 'explicitly': 0.05; 'explicit': 0.07; 'committing': 0.09; 'consistency': 0.09; 'bug': 0.12; 'changes': 0.15; '(either': 0.16; 'adam': 0.16; 'begin.': 0.16; 'downside': 0.16; 'from:addr:awilliam': 0.16; 'from:addr:whitemice.org': 0.16; 'from:name:adam tauno williams': 0.16; 'received:72.14.190': 0.16; 'received:72.14.190.87': 0.16; 'received:mail.wmmi.net': 0.16; 'received:wmmi.net': 0.16; 'then?': 0.16; 'subject:python': 0.16; 'app': 0.19; 'backend': 0.19; 'commit': 0.19; '>>>': 0.22; 'header:User-Agent:1': 0.23; 'issue,': 0.24; 'williams': 0.24; 'mention': 0.26; 'least': 0.26; 'header:In-Reply-To:1': 0.27; 'work.': 0.31; 'code': 0.31; 'easier': 0.31; 'subject:Database': 0.31; 'received:72.14': 0.33; 'transaction': 0.35; 'url:org': 0.36; 'should': 0.36; 'received:10': 0.37; 'to:addr:python-list': 0.38; 'anything': 0.39; 'does': 0.39; 'sure': 0.39; 'to:addr:python.org': 0.39; 'changed': 0.39; 'how': 0.40; 'read': 0.60; 'units': 0.60; 'break': 0.61; "you're": 0.61; 'real': 0.63; 'happen': 0.63; 'dont': 0.67; 'ate': 0.84; 'subject:via': 0.84
User-Agent: K-9 Mail for Android
In-Reply-To: <CALwzidnQM6Ae2DH1FsXX_cMx8JHS_=pf8hSyQPFMO=0iAjMnkg@mail.gmail.com>
References: <l2pois$359$1@dont-email.me> <mailman.757.1381001416.18130.python-list@python.org> <l2ppnh$9fc$1@dont-email.me> <CALwzidnQM6Ae2DH1FsXX_cMx8JHS_=pf8hSyQPFMO=0iAjMnkg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Subject: Re: Database statements via python but database left intact
From: Adam Tauno Williams <awilliam@whitemice.org>
Date: Sun, 06 Oct 2013 11:52:11 -0400
To: Python <python-list@python.org>
X-BeenThere: python-list@python.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: General discussion list for the Python programming language <python-list.python.org>
List-Unsubscribe: <https://mail.python.org/mailman/options/python-list>, <mailto:python-list-request@python.org?subject=unsubscribe>
List-Archive: <http://mail.python.org/pipermail/python-list/>
List-Post: <mailto:python-list@python.org>
List-Help: <mailto:python-list-request@python.org?subject=help>
List-Subscribe: <https://mail.python.org/mailman/listinfo/python-list>, <mailto:python-list-request@python.org?subject=subscribe>
Newsgroups: comp.lang.python
Message-ID: <mailman.787.1381076555.18130.python-list@python.org>
Lines: 17
NNTP-Posting-Host: 2001:888:2000:d::a6
X-Trace: 1381076555 news.xs4all.nl 15906 [2001:888:2000:d::a6]:45456
X-Complaints-To: abuse@xs4all.nl
Xref: csiph.com comp.lang.python:56267

>>> Are you sure that you're committing your changes (either by having
>>> autocommit set or using an explicit con.commit() call)?
>>> http://geert.vanderkelen.org/dont-forget-the-commit-in-mysql/
>> I dont think that is the issue, because up until now i never used
>commit and
>> all transaction were successfully were happening.

Depending on autocommit is a bug [when does commit happen then?  consistency is a real problem].  Code should always explicitly ate least COMMIT or ROLLBACK if not explicitly BEGIN.  Not to mention how much easier it makes it to read the code and understand the units of work.

>Well, have you changed anything in your database configuration?

a big downside of autocommit - backend changes can break you app



-- 
Adam Tauno Williams