Florent Aide schrieb: > We could try to mimic the session_mapper behavior (it is documented in > the SQLAlchemy documentation) but I would rather avoid this cruft and > explain how to migrate from the old SQLAlchemy way to the new one... > > What do others out there think?
This is nice, but I agree with the other Christophs that it at least should be configurable. The old session_mapper behavior was quite handy, and the migration can be tedious and error prone if you do not have a good enough test suite. Actually, the main reason for people to use 1.1 instead of 2.x is that they want to avoid this migration hassle. -- Christoph --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
