@voltro/database 0.74.0 → 0.75.0

package/dist/sql.d.ts

@@ -161,13 +161,7 @@ declare type AnyView = View<string, Record<string, ColumnDefinition<unknown>>>;
  */
 export declare const appliedAtValue: (sql: SqlClient.SqlClient, iso: string) => Effect.Effect<string>;
 
-/**
- * The ids recorded as applied file migrations on THIS database — exported for
- * the deploy compensation, which compares the set before a run with the set
- * after it to know which `down`s to run. An absent ledger table reads as an
- * empty set: a virgin database has applied nothing.
- */
-export declare const appliedFileMigrationIds: (sql: SqlClient.SqlClient) => Effect.Effect<ReadonlyArray<string>, never>;
+export declare const appliedFileMigrationIds: (sql: SqlClient.SqlClient) => Effect.Effect<ReadonlyArray<string>, SqlError_2>;
 
 /**
  * The applied file migrations WITH the body hash recorded at the time.
@@ -181,7 +175,7 @@ export declare const appliedFileMigrationIds: (sql: SqlClient.SqlClient) => Effe
 export declare const appliedFileMigrations: (sql: SqlClient.SqlClient) => Effect.Effect<ReadonlyArray<{
     readonly id: string;
     readonly hash: string;
-}>, never>;
+}>, SqlError_2>;
 
 /**
  * The operations the resume ledger says RAN — `started`, `added` or `applied` —
@@ -2620,6 +2614,21 @@ export declare const ensureDeployLedgerTable: (sql: SqlClient.SqlClient, dialect
  */
 export declare const ensureLedgerTable: (sql: SqlClient.SqlClient, dialect: DialectId) => Effect.Effect<void, SqlError_2>;
 
+/**
+ * The PLAN ledger (`_voltro_migration_plans`) — same bootstrap, one caller.
+ *
+ * A file migration records itself here, and the file pass runs BEFORE the
+ * planner that would otherwise create this table. On a database that does not
+ * have it yet, `up()` therefore succeeded and the recording INSERT failed —
+ * `FileMigrationLedgerError`, the one outcome whose whole message is "do not
+ * re-run this". Same reason the resume ledger above is created by the applier
+ * rather than planned: a run needs it before any DDL of its own has happened.
+ *
+ * Index-free like the others, so the planner still owns the table's shape and a
+ * re-plan converges by adding the indexes it declares.
+ */
+export declare const ensurePlanLedgerTable: (sql: SqlClient.SqlClient, dialect: DialectId) => Effect.Effect<void, SqlError_2>;
+
 /** Exported for the same reason as {@link enumTypeBlocks}, and it MUST run
  *  before it — see that function's note on ordering. */
 export declare const enumRenameBlocks: (tables: ReadonlyArray<AnyTable>, dialect: DialectId) => string;
@@ -2853,6 +2862,9 @@ export declare interface FileMigrationContextInput {
  * Its own error type because the recovery is the opposite of the ordinary one:
  * do NOT re-run. The change has landed; what is missing is the record that says
  * so, and every future invocation will apply it again until that row exists.
+ * Unless the write failed because the row is ALREADY there — another process
+ * recorded the same migration — and then the message says the opposite: the
+ * record is correct and the body ran twice.
  */
 export declare class FileMigrationLedgerError extends Error {
     readonly migrationId: string;