[SQLObject] Minor problem with set method

[James R. <jcr...@ya...>]

While playing with SQLObject, I ran into a problem
with the "set" method.  If an exception occurred
during an update (i.e. invalid data sent to the
server), the exception is properly raised to the
caller.  But, any subsequent "set" calls causes "a
freeze." I know that, technically, the data should be
validated before sending it to the db, but... 

To make a long story short, I had to add a try/finally
block after the call to self._SO_writeLock.acquire()
in the SQLObject.set method so that the
self._SO_writeLock.release() always gets called.  

Will this break anything?

James

__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com