On 5/23/06, Jorge Godoy <[EMAIL PROTECTED]> wrote: > 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.
Sounds doable, ActiveMapper is mostly syntactic sugar if I understand it correctly. I originally had a working (though incomplete) sqlalchemy provider that didn't use ActiveMapper, and used the same table structure/naming as SO. It's a while since then though and things have probably changed, modifiying current soprovider will probably be easier. > 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.) I'll give it a try.. :o) Arnar --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
