> > > > 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).
I agree. But I'm going to sing my usual song here: Please do not change this until it has been documented with at least some sort of minimal newbie friendly write up on Elixir and how the defaults are set up. I think component changes have been outpacing the docs in that regard. We mustn't lose sight of the new user experience in the race for best-of-breed! Iain --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
