On 5/30/06, Jorge Godoy <[EMAIL PROTECTED]> wrote: > Em Terça 30 Maio 2006 10:26, Arnar Birgisson escreveu: > > > Maybe we could then have a config option, akin to "always allow json" > > that would in effect wrap all controller-methods in such a decorator. > > Turning that option on, wouldn't we acheive what Kevin suggested > > earlier? > > This sounds good to me... I like it. And it is backwards compatible.
For a first test, I'm trying to port the current code over to 0.2. This means that in "run_with_transaction", I create a session and store it as a global object in turbogears.database - this session gets flushed after running the controller. However, in the identity/visit frameworks, I need a session to make queries to the database. Should I: a) create an explicit Session for those queries and close them afterwards b) rely on this "automatic" session to be in place in turbogears.database so the insert/updates for tg_visit and tg_visit_identity get commited at the end of the request? Sorry if this is a stupid question, I'm a bit unclear on TG internals still. 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 -~----------~----~----~----~------~----~------~--~---
