-> It sounds like a glitch in the DA. Well, this is what I found. The attribute "lock" is being accessed in the _abort method, which is: -------------------------------------- def _abort(self, *ignored): try: self.db.query("ROLLBACK") self.db.store_result() finally: self.lock.release() -------------------------------------- It's failing in the finally: block, trying to access self.lock.release(). But this is all I see in the __init__ method of the class DB(TM): definition: self._lock = allocate_lock() In fact, I see this "self._lock" attribute, *with the underscore*, seven other times in the the file. But I see a self.lock attribute appear three times in the file -- but never in the __init__ method. So, as I understand it, unless self.lock appears in the __init__ method of the parent class "TM", then "self.lock" is a typo and should be "self._lock". Is that a valid assumption? Notice that TM does not declare self.lock: [root@dev ZRDB]# pwd /usr/share/zope/lib/python/Shared/DC/ZRDB [root@dev ZRDB]# grep -i lock TM.py [root@dev ZRDB]# Should I change those three instances of self.lock to be self._lock? Also, what is the last known *WORKING* version of the Z MySQL Database Adapter? This seems like a showstopper bug, but it's in a product that has to be pretty popular... -> Alternatively, delete and recreate the DA object. This I do not understand. How would simply deleting and re-creating an instance fix a bug in the code? Thanks, Derek

-> Should I change those three instances of self.lock to be -> self._lock? More info: doing this fixed my problem. I am shocked and amazed that a product that *must* be one of the most popular around could have a typo in it (assuming, of course, that this is the Correct Fix for this particular problem). What's worse, this bug was caused by another (imho) "bug", see below for details. What am I missing? Did I install an unstable beta release? This is version 2.0.9, the latest I could find. I was recommending Zope + MySQL as a solution for my client, but these basic, rudimentary errors are changing my mind. Version 2.0.9 and not even the fscking "test" page works... what is up with that? Thanks, Derek P.S.> What was happening: I was testing with the string SELECT * FROM applicants; This results in an exception, caused by (imho) another "bug" in the database adapter. It limits the number of results to 1000 on SELECT for whatever reason -- but when it adds the LIMIT code, it does not remove the ";" at the end. Here is the relevant code: if qtype == "SELECT" and max_rows: qs = "%s LIMIT %d" % (qs,max_rows) r=0 db.query(qs) This results in an SQL code error, ala this result: Error Value: (1064, "You have an error in your SQL syntax near '; LIMIT 1000' at line 1") So changing my test string from "select * from applicants;" to "select * from applicants" fixed my problem. I assume I'll have a similar problem when I write my Z SQL method. Anyway, the SQL sytax error resulted in an exception, which resulted in a call to _abort(), which tried to access self.lock (instead of self._lock). Thank god I've been working with Python lately. This and stories of severe memory corruption in Zope 2.4.3 are highly disturbing.

-> Well, for what its worth, Andy made those changes to the DA based on -> some stability feedback I'd given him, and because he probably didn't -> get a whole lot of people testing the beta, it slipped through. Okay, I've calmed down now. I apologize for my earlier outburst. After RTFM'ing Z SQL Methods, and seeing that they are not supposed to have ';' at the end, I guess that is not really a problem in the MySQL adapter. And if there were no beta testers who caused _abort() to get called, this bug could easily have slipped through. So this is not as serious as it seemed. (Although why a global substition of self.lock for self._lock wasn't done, I'll never know :) Thank you Matthew for your help. I would appreciate it if you could forward on this bug to the MySQL Database Adapter maintainer. --Derek

-> No idea, don't use MySQLFolder. This is for the MySQL Database Adapter, not user authentication. --Derek