DatabasePolicy

@Serializable
enum DatabasePolicy : Enum<DatabasePolicy> (source)

How the ScenarioOrchestrator should handle an existing <analysisName>.db file at the start of a Simulate. Stored on OutputConfig.databasePolicy.

Entries

Link copied to clipboard

Delete the existing <analysisName>.db (if present) before the run, then create a fresh database. Re-running the same analysis replaces the prior database file in-place; only the most recent run's data is kept on disk. The default — matches the most common workflow where the user iterates on a configuration and only cares about the latest results.

Link copied to clipboard

Keep any existing <analysisName>.db untouched and open a new database at <analysisName>_<yyyy-MM-dd_HHmmss>.db alongside it. Both files survive on disk — the user can compare runs across time. Disk usage accumulates; periodic cleanup is the user's responsibility.

Properties

Link copied to clipboard

Returns a representation of an immutable list of all enum entries, in the order they're declared.

Functions

Link copied to clipboard

Returns the enum constant of this type with the specified name. The string must match exactly an identifier used to declare an enum constant in this type. (Extraneous whitespace characters are not permitted.)

Link copied to clipboard

Returns an array containing the constants of this enum type, in the order they're declared.