On Jun 28, 2007, at 6:11 PM, Florent Aide wrote:
> > Hum... > > +0 on this. I do a _lot_ of plain SA in my work hours and I also do a > lot of plain SA in TG or other for home grown projects and I would > expect TG to come with plain SA by default. > > The SA docs are really good and the expressiveness of plain SA is sooo > excellent... We can always have an elexir optional switch on the > command line... > > As a newcomer to any project boasting to support SA I would expect the > project to have a plain SA mode and not "hide" it inside some wrapper. > > If a lot of people prefer to have elexir as default, so be it. But > then at least provide plain active_mapper SA as an option. > AFAK, Elixir defined Entities are still SA mapped classes on the inside. This means that whatever session and transaction machinery TG uses internally should cope equally well with both kind of ways to declare model objects. I see no reason, a priori, that would prevent the use of plain SA classes in a specific project, even if the quickstarted template and documentation encourages Elixir (which after all is what TG philosophy is about: provide good defaults to get on speed quickly on 95% of projects, but make the specific needs of the other 5% possible with some extra effort). Alberto --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
