bx-orm-transactions

ORM transactions in BoxLang ensure atomic saves by wrapping multiple entity operations in a transaction block that automatically commits on success and rolls back on error. This prevents partial data writes when errors occur.

BoxLang ORM nested transactions use savepoints to allow partial rollbacks within a larger transaction block. You can set intermediate savepoints, roll back to them on specific errors, and still preserve the outer transaction without aborting the entire operation.

Yes, BoxLang ORM transactions support multi-datasource configurations, allowing you to coordinate transaction blocks and session management across different datasources within the same application workflow.

Use ORMFlush within a BoxLang ORM transaction to force pending changes to the database, and use ORMClearSession to clear the session cache. Both coordinate in-session changes across multiple entities during active transaction blocks.

BoxLang ORM provides explicit commit and rollback functions for manual transaction control, allowing you to override the automatic commit-on-success and rollback-on-error defaults when you need custom logic or conditional saves.