On Sunday, February 17, 2013 10:06:33 AM UTC-7, [email protected] wrote: > > [...] > My question is how is this normally managed in typical > application code? A flush can potentially occur anytime a > mapped attribute is changed. Do I need to wrap every such > place in my code in a try/except to catch a possible error > and do the rollback? >
Nevermind, I just found http://www.sqlalchemy.org/trac/wiki/FAQ#SessionsTransactions which answers this question: yes, so limit/centralize the number of places in your code where you need to do so. -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sqlalchemy?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
