Well for me, I think in my production stuff I'll stick with sacontext and sqlalchemy 3x until this sorts out a little. Having said that I will play with the new stuff in a separate workingenv to get a taste of how things are going to work in the near future.
What would be really nice is if pylons had an "sqlalchemy" template that added some of the code mentioned in the tutorial, maybe it could add everything that is needed to for single default database? then all we would have to do is edit the model, as I'm sure I'll forget one or two configuration things and spend lots of time chasing my tail trying to figure out why my simple query is not working :) Jose On 8/16/07, Michael Bayer <[EMAIL PROTECTED]> wrote: > > > ive released beta3 which fixes the remove() issue. > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
