@voltro/database 0.4.0 → 0.6.0

package/dist/sql.d.ts

@@ -2003,6 +2003,24 @@ declare interface TableUnique {
     };
 }
 
+/**
+ * Clear the `blocked` flag on every LOSSY operation in a plan.
+ *
+ * Called only after the destructive opt-in has been established, and it is not
+ * cosmetic. `applyPlan` carries its OWN unconditional refusal on any blocked
+ * operation, with no override parameter. So a plan that the boot gate has
+ * decided may proceed, but which still arrives marked blocked, is refused a
+ * second time by the applier — which meant `VOLTRO_DESTRUCTIVE_OK=1` could
+ * never actually drop a table. The planner's fix hint names that exact
+ * variable, so the documented escape hatch pointed at a wall.
+ *
+ * Only `lossy` ops are unblocked, and callers must have already established
+ * that no other class is blocked. A rename-without-marker or a NOT NULL
+ * without backfill stays blocked even in destructive-OK mode: those lose data
+ * regardless of intent, so intent is not the question being asked.
+ */
+export declare const unblockLossy: (plan: MigrationPlan) => MigrationPlan;
+
 /**
  * Unique-constraint metadata. Set by `.unique()` (or `.unique({ dedup })`).
  *