RefreshDatabase

The parameters that should be used when running "migrate:fresh".

Determine if views should be dropped when refreshing the database.

Determine if types should be dropped when refreshing the database.

Determine if the seed task should be run when refreshing the database.

Determine the specific seeder class that should be used when refreshing the database.

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.

Define hooks to migrate the database before and after each test.

For tests using RunTestsInCoroutine, the transaction and post-refresh hooks are deferred to setUpRefreshDatabaseInCoroutine() to keep all transaction state in the same coroutine.

Refresh the model booted states.

Restore the in-memory database between tests.

Determine if any of the connections transacting is using in-memory databases.

Determine if a given database connection is an in-memory database.

Refresh a conventional test database.

Runs migrations if needed. For non-coroutine tests, also starts the wrapper transaction. For coroutine tests, transaction handling is deferred to setUpRefreshDatabaseInCoroutine().

Start database transaction in the test coroutine.

Called by RunTestsInCoroutine before the test runs. Maintains correct ordering: transaction starts, then afterRefreshingDatabase runs, then test executes. This keeps all transaction state in the same coroutine.

Note: restoreInMemoryDatabase() runs earlier in refreshDatabase() before migrations, which is the correct ordering for in-memory SQLite.

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.

Perform any work that should take place before the database has started refreshing.

Perform any work that should take place once the database has finished refreshing.

No description