[EMAIL PROTECTED] schrieb: > So yesterday I finally took the plunge and converted a stand alone > utility used to support my site to sqlalchemy. > > Today I'd like to use sqlalchemy for a new feature I'm writing in my > core controller. > > Is this something I can do while continuing to use sqlobject at the > same time? > > Obviously I'll try to avoid intermingling writing to the same row from > both at the same time. > > But other than that am I likely to run into caching issues? Or what > issues might I run into? How can I minimize them? > > My program is little complex to switch from sqlalchemy to sqlobject > all in one fell swoop. So if I could use both for a while, and slowly > refactor the code to sqlalchemy that would be nice. > > (Side note: I'm very impressed by the level of support Michael Bayer > pays to the sqlalchemy mailing list.)
I wouldn't recommend using them both *on the same dataset*. Both do caching (in my limited experience, SA does even more that SO) - and you will introduce hard to track bugs when modifying rows using one and then querying with the other. Diez --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
