historyPlanfunctionfunction historyPlan(files: readonly Artifact[], folder?: string): Result<RunPlan & { readonly dialect: string; }, readonly ReplayError[]>The plan a history holds.
Replaying a history (commons data 0018-sql-history FR-005, FR-006): the manifest and every file are checked, then what the files say is run through the lifecycle's run, with its ledger, its transactions, its checks, its guards and its base, so that replaying the files is running the plan they were frozen from.
historyPlanfunctionfunction historyPlan(files: readonly Artifact[], folder?: string): Result<RunPlan & { readonly dialect: string; }, readonly ReplayError[]>The plan a history holds.
replayfunctionfunction replay(files: readonly Artifact[], driver: Driver, dialect: Dialect, options: RunOptions & { readonly folder?: string | undefined; }): Promise<Result<Applied, readonly ReplayError[]>>Replays a history on a database.
| Parameter | What it is |
|---|---|
files | the files of the history |
driver | the database |
dialect | its dialect |
options | what the run is given, and the folder |
Returns: what was applied, or why not
ReplayErrortypeno test imports ittype ReplayError = { readonly kind: "history"; readonly problems: readonly Problem[] } | { readonly kind: "empty" } | RunError;What is wrong with a replay.