Sorry, this was meant for the list. Arnar
---------- Forwarded message ---------- From: Arnar Birgisson <[EMAIL PROTECTED]> Date: May 30, 2006 1:22 PM Subject: Re: [TurboGears] Re: SQLAlchemy 0.2 To: Jorge Godoy <[EMAIL PROTECTED]> Kevin: You made a good point, I agree we should minimize the boilerplate (which is the very thing that makes one look at TG in the first place). On 5/30/06, Jorge Godoy <[EMAIL PROTECTED]> wrote: > What I was picturing on my mind was something like: > > - make it like the latter > - provide a default session that implements the first option > - make this default configurable in app.cfg and enabled > > I believe this will make the transition smoother and keep things working "as > expected". Sounds good. I'll look into that. And no, making this configurable should not be to hard. One question though, where would the appropriate place to store the default session be? > What I always believe we need is to able to just replace our model and > specific idioms from SO to SA and have it working. If we need to add new > code in our controllers then we're loosing something. Of course, if it is > inevitable then we have no choice. It should be possible, but I think we shouldn't make the SA end more complicated / less logical to acheive that. Changing your project from SO to SA mid-project would be no easy task if you had a complex model - so maybe keeping the two compatible is a moot point? Arnar --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
