Florent Aide schrieb: > I made some tentative to shy from my responsibilities by pushing the > breaking change to later-on :p, but obviously people remarked that and > won't let me do so :) > It would be better to break compatibility a little bit now (and > provide upgrade instructions) for people who were using SA already > than introduce SA to a lot of people and then break SA support in a > few weeks.
I agree that we should make these changes now before 1.1 is widely adopted. Actually I think we don't even need to break compatibility. We can continue to provide the contextual mapper as tg.database.mapper for backward compatibility and people who like using it, but we shouldn't promote this usage any more in TG >= 1.1 and probably rewrite the model templates to use the declarative style starting with 1.1 already, and revise identity to work with a default mapper as well (it currently assumes a contextual mapper), which is quite simple. Maybe TG 1.1 should also require SA 0.4 and TG 1.5 could even require SA 0.5, so we will not be burdened with supporting the outdated versions. See also Michael's answer on the SA mailing list here: http://groups.google.de/group/sqlalchemy/browse_frm/thread/bc7ecb50a4ef597c/339422762b06f1fb?tvc=1#339422762b06f1fb We should also create a trac ticket and move this discussion to tg-tunk. -- Christoph --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
