Christoph Zwerschke schrieb: > 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.
After having a second look I noticed that after some polishing (already done in r6633) this is not a real problem. The old Session.mapper is still available as turbogears.database.mapper as long as it's available in SA. So old projects will continue to work with SA < 0.6 (emitting a deprecation warning for SA >= 0.5.5). Internally however, TG 1.1 now uses only the standard mapper, so it is compatible with SA >= 0.5.5 now. The quickstart templates now also imports the standard mapper, but there is a comment mentioning that you can also use database.mapper instead. So this is "configurable" via the "import mapper from ..." in model.py. -- 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 -~----------~----~----~----~------~----~------~--~---
