That's odd. SQLObject is threadsafe. It's possible that he was using SQLObject 0.6.1, which was the current stable version at the time. SQLObject 0.7 had quite a bit of work done on it, so it's entirely possible that it's easier today than it was then.
Kevin On 10/22/05, Todd Greenwood <[EMAIL PROTECTED]> wrote: > > Looks a bit sticky. As mikerobi has stated that it's a wontfix due to > complexity and that 'sqlobject is not 100% thread safe'. Perhaps we > should get the SQLObject folks to talk to the CP folks? > > -Todd > > Mon 22 Aug 2005 03:25:22 PM CDT: Modified by mikerobi > > * resolution set to wontfix > * status changed from assigned to closed > > An sqlobject adaptor requires uneccessary complexity do to convertion > to and from python dictionarys. The sqlobject adaptor has been dropped. > A driver based on PyDO2 will take its place. (I am not against > including an sqlobject adaptor if someone else would like to contribute > it, but I suggesting waiting till after I release the PyDO adaptor, so > you can see how column names are handled.) > > -- Kevin Dangoor Author of the Zesty News RSS newsreader email: [EMAIL PROTECTED] company: http://www.BlazingThings.com blog: http://www.BlueSkyOnMars.com
