DatabaseTransactions

Rewrite the default connection's database name for parallel testing.

Config-only — does not create connections or purge pools. Called early in CreatesApplication (after config is loaded, before defineEnvironment) so that custom connections derived from the default connection inherit the per-worker database name.

No-op when not running in parallel or when using in-memory SQLite.

Ensure the per-worker database exists, creating it if needed.

Called from database testing traits (RefreshDatabase, DatabaseMigrations, DatabaseTransactions) after the app is booted and connections are available. The config has already been rewritten by configureParallelDatabaseName().

No-op when not running in parallel or when using in-memory SQLite.

Determine if the database should be managed for parallel testing.

Get the per-worker test database name.

Handle database transactions on the specified connections.

For tests using RunTestsInCoroutine, this method does nothing - the actual transaction work is done in setUpDatabaseTransactionsInCoroutine() to keep all transaction state in the same coroutine.

For non-coroutine tests, this starts the transaction immediately and registers a rollback callback.

Start database transaction in the test coroutine.

Called by RunTestsInCoroutine before the test runs. Keeps all transaction state in the same coroutine, avoiding Context handoff issues.

Rollback database transaction in the test coroutine.

Called by RunTestsInCoroutine after the test runs.

Start transactions on all connections.

Rollback transactions on all connections.

The database connections that should have transactions.