Re: MySQLdb - Query/fetch don't return result when it *theorically* should

2006-01-26 Thread Mark Hertel
On Wed, 18 Jan 2006 18:31:39 -0500, Bernard Lebel [EMAIL PROTECTED] wrote: I'm absolutely flabbergasted. Your suggestion worked, the loop now picks up the changed values, and without the need to reconnect. It's the first time I have to commit after a query, up until I wrote this program, I

Re: MySQLdb - Query/fetch don't return result when it *theorically* should

2006-01-19 Thread Alan Franzoni
Bernard Lebel on comp.lang.python said: I'm absolutely flabbergasted. As I told you, i think this is related to the isolation level - I really think it's a feature of the DB you're using - this way, until you commit, your database lies in in the very same state on the same connection. Suppose

Re: MySQLdb - Query/fetch don't return result when it *theorically* should

2006-01-19 Thread Bernard Lebel
Thanks a lot for the explanations Alan. That really helped. Bernard On 1/19/06, Alan Franzoni [EMAIL PROTECTED] wrote: Bernard Lebel on comp.lang.python said: I'm absolutely flabbergasted. As I told you, i think this is related to the isolation level - I really think it's a feature of

MySQLdb - Query/fetch don't return result when it *theorically* should

2006-01-18 Thread Bernard Lebel
Hello, I'm stumbled at a serious problem, and quite frankly getting desparate. This is a rather long-winded one so I'll try to get straight to the point. I have this Python program, that performs MySQL queries to a database. These queries are performed at regular intervals. Basically it is

Re: MySQLdb - Query/fetch don't return result when it *theorically* should

2006-01-18 Thread Bernard Lebel
Oops, sorry: link to sources http://www.bernardlebel.com/scripts/nonxsi/help/ Thanks again Bernard On 1/18/06, Bernard Lebel [EMAIL PROTECTED] wrote: Hello, I'm stumbled at a serious problem, and quite frankly getting desparate. This is a rather long-winded one so I'll try to get

Re: MySQLdb - Query/fetch don't return result when it *theorically* should

2006-01-18 Thread Bernard Lebel
Btw I have tried running much simpler versions of the query, like SELECT * FROM TB_CURRENT_JOBS WHERE Status = 'Pending', but yet again I get the same results. *sigh* Bernard On 1/18/06, Bernard Lebel [EMAIL PROTECTED] wrote: Oops, sorry: link to sources

Re: MySQLdb - Query/fetch don't return result when it *theorically* should

2006-01-18 Thread Bernard Lebel
Strange, I have just found out that all queries past the first one always behave the same way: they return the very first result. Somehow, the program seems to keep in memory the query results. I hope people don't mind if I'm doing the confessional way of debugging, but I've been knocking my

Re: MySQLdb - Query/fetch don't return result when it *theorically* should

2006-01-18 Thread Alan Franzoni
Il Wed, 18 Jan 2006 14:39:09 -0500, Bernard Lebel ha scritto: [cut] 1) It would be great if you didn't post four messages in less than an hour ^_^ 2) Your code is very long! You can't expect many people to run and read it all! You should post a very small demo program with the very same problem

Re: MySQLdb - Query/fetch don't return result when it *theorically* should

2006-01-18 Thread Bernard Lebel
Hi Alan, On 1/18/06, Alan Franzoni [EMAIL PROTECTED] wrote: Il Wed, 18 Jan 2006 14:39:09 -0500, Bernard Lebel ha scritto: 1) It would be great if you didn't post four messages in less than an hour ^_^ Yeah I know :-) But like I said, I've been stuck for 3 days on that, so, I need to get

Re: MySQLdb - Query/fetch don't return result when it *theorically* should

2006-01-18 Thread Stephen Prinster
Have you tried doing a connection.commit() after each query attempt? I believe mysqldb also has a connection.autocommit feature. -- http://mail.python.org/mailman/listinfo/python-list

Re: MySQLdb - Query/fetch don't return result when it *theorically* should

2006-01-18 Thread Bernard Lebel
I'm absolutely flabbergasted. Your suggestion worked, the loop now picks up the changed values, and without the need to reconnect. It's the first time I have to commit after a query, up until I wrote this program, I used commit() was for UPDATE/INSERT types of commands only, and always got