hey julien, On 11/16/2011 02:14 PM, julien tayon wrote: > 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 ? i wouldn't have explained it better :) btw the transaction object is there for the case of multiple sessions. otherwise, dbsessions can handle these semantics too. > > Is that it, or did I miss something, if so I am a lousy teamate :) as i said. the answer began to seed in diez's post about session objects i wasn't aware of, then jonathan came with the solution. > I love to understand and I am a quick learner, so I'll understand a > terse answer. once i've asked the guard at a swimming pool whether he could traverse the pool under the water. he told me the would do it for 100$. and i told him the money wpuld be worth if he taught me to do it. i asume you would have done the same ;) > > thanks for giving me my batch of complex problems everyday since > somedays I fear to die from boredom. i can't say how complex it was. it's just how rusty i am on tg. well, it will improve again, i hope. > best regards, alex
-- 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.
