Yeah, everything looks fine. Just wondering if I can save some overhead by checking for dirty state myself, or if that's not worth it.
On Feb 22, 8:35 am, Michael Bayer <mike...@zzzcomputing.com> wrote: > calling commit() on every request is fine, as long as you aren't creating > unwanted 'dirty' state inadvertently. Watching your SQL logs could help > you to determine if things are happening that are undesirable. > > On Feb 21, 2011, at 3:38 AM, Romy wrote: > > > > > > > > > Switched to autocommit=False, and calling commit(), followed by > > remove() on every end-of-request, regardless of whether there's data > > to commit or not. > > > Am I adding any unnecessary overhead ? And if so, how should I be > > checking for dirtyness prior to committing ? > > > R > > > -- > > You received this message because you are subscribed to the Google Groups > > "sqlalchemy" group. > > To post to this group, send email to sqlalchemy@googlegroups.com. > > To unsubscribe from this group, send email to > > sqlalchemy+unsubscr...@googlegroups.com. > > For more options, visit this group > > athttp://groups.google.com/group/sqlalchemy?hl=en. -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com. To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
