Em Terça 23 Maio 2006 10:27, Arnar Birgisson escreveu: > I'm having the same problem as Minh, but the error in !833 seems to be > a different one, although they both affect quickstarted projects with > sqlalchemy. Also, Godoy was using sqlalchemy 0.1.6 but Minh 0.1.7 - if > that makes a difference.
The same happens with 0.1.7... I did a lot of changes to SQL Alchemy (SA) code in TG based on other people tickets and some hacks of my own. This helped fixing some things but I haven't stopped, again, to fix all classes. Today's status is that a project with SA isn't runnable because of some loops with ActiveMapper code in SA. > Has anyone figured out the reason for this thread._local error? Is > there a workaround until this is fixed? Yes, it is fixed, but there's the loop problem to be solved. > I need to write a TG app using an older database schema, which I can > only do with sqlalchemy. This is a simple utility-app only used in the > IT dept. so the issue of stability or production-quality is not that > big for me. If you could remove all ActiveMapper occurrences from TG's code -- savisit.py, saprovider.py and model.py -- keeping compatibility with SQL Object's class names (my idea is having both mechanisms interchangeable right from the start, i.e., I can use the same database using any of these two ORMs without having to worry about changing or duplicating something on the database) I'd apply the patch to TG. I just couldn't spend more time on the migration, yet. But I believe that this is all there is to be fixed to have it working... (At least, this is where I stopped.) -- Jorge Godoy <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears -~----------~----~----~----~------~----~------~--~---
