Hello, Just for the sake of understanding, can you enlighten us on the bug ?
So far this is what I may have understood : - All sqlalchemy actions in a controller is inside a DBSession thus in SQL in a context of Transaction Begin/Commit/Rollback ; - you were in a controller and did only raw SQL ? ; - and as raw SQL does not mark the session changed, therefore it does not commit at the end of the session (on return of the controller) ? - as a result you have to force DBsession as changed to force the commit ? Is that it, or did I miss something, if so I am a lousy teamate :) I love to understand and I am a quick learner, so I'll understand a terse answer. thanks for giving me my batch of complex problems everyday since somedays I fear to die from boredom. -- hf, gl Jul -- 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.
