Florent Aide schrieb: > At the moment I have just replaced the session mapper with the > sqlalchemy.orm.mapper. BUT this means that user code that relied on > the session_mapper behaviour (instanciating the object with arguments, > auto saving, query method on the class) will break. > > 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?
I tend to disagree. I think this would require extensive changes to many TG1 apps out there. I would prefer if TG1.1 provided a compatibilty layer, that provides as much of the old mapper functionality as can be reasonably implemented without much effort. It could still issue deprecation warnings when used. On the other hand, people can always use the old SQLAlchemy releases for their TG1 apps... Chris --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
