Strange problem: MySQL and python logging using two separate cursors

Frank Aune Frank.Aune at broadpark.no
Fri Jan 11 05:00:54 EST 2008


On Wednesday 09 January 2008 18:52:02 Dennis Lee Bieber wrote:
> On Wed, 9 Jan 2008 10:11:09 +0100, Frank Aune <Frank.Aune at broadpark.no>
>
> declaimed the following in comp.lang.python:
> > The only clue I have so far, is that the cursor in task 1 seems to be
> > unable to "register" any new entries in the log table produced by task 2
> > as soon as task 1 perform an SQL query of some kind.
>
> 	How often do you issue a commit? 

I experience the behaviour for task 1 even if the select query only reads out 
data and no commit is needed.

Do I really need to perform commits on a handler even though it only reads out 
data? From a MySQL shell I can see the changes from the other handler without 
the commits, but afaics that shouldnt be the case if the above were true.

Thanks,
Frank




More information about the Python-list mailing list