you just have the overhead of the empty "commit" itself, which might not be any
different than the empty "rollback" that occurs otherwise (well it occurs no
matter what actually)
On Feb 23, 2011, at 8:02 PM, Romy wrote:
> Yeah, everything looks fine.
>
> Just wondering if I can save some
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 wrote:
> calling commit() on every request is fine, as long as you aren't creating
> unwanted 'dirty' state inadvertently.
