On Thursday 28 December 2006 20:58, Oleg Broytmann wrote: > On Thu, Dec 28, 2006 at 07:50:23PM +0100, Markus Gritsch wrote: > > Well, this would not solve the problem intoduced with SQLObject 0.8. > > An Error 2006 occurres in the following scenario using SQLObject 0.7: > > * My application is running, being connected to the MySQL database. > > * The MySQL service is stopped and restarted. > > * Every query from now on on the already made connection fails with > > the Error 2006. > > So the solution for now, I think, would be to stop testing for the > error 2006 and raise an error.
Please don't do this. 2006 is returned more often than 2013 (read the comments in the patch I submitted). The problem Markus has is that his mysqldb module will never reconnect because it doesn't set the reconnect flag. This is why he gets 2006 over and over. Please consider the patch I submitted as it fixes the problem both for those that use the original mysqldb module (that doesn't reconnect) and for people who use a modified mysqldb module that does reconnect. With your change the latter group will no longer be able to reconnect as 2006 is raised first and is no longer handled. -- Dan ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ sqlobject-discuss mailing list sqlobject-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
