IMHO it's not a micro-optimization. RDBMs systems will often take a
performance hit on the COMMIT vs rollback when there are multiple
simultaneous transactions, and it can cause issues on clustered/replicant
systems.
I often forget about this too. The techniques that have worked for me:
*
My understanding is that it’s a micro optimization that a rollback is slightly
more efficient than a commit. I’m not aware of any good arguments against
defaulting to changed. Would need to ask the zope.sqlalchemy folks for some
insights.
- Michael
> On May 2, 2022, at 17:55, Theron Luhn
I’m using a cookiecutter-based Pyramid+zope.sqlalchemy+SQLAlchemy stack. More
and more lately I’ve been skipping the ORM and using Core for write operations,
and I frequently run into issues where I forget to mark_changed and
zope.sqlalchemy ROLLBACKs by default:
> By default, zope.sqlalchemy
