@voltro/database 0.20.2 → 0.21.0

package/dist/sql.d.ts

@@ -550,6 +550,31 @@ export declare interface ColumnSnapshot {
         readonly from: ColumnType;
         readonly using?: string;
     };
+    /**
+     * Bounded text length from `text().maxLength(n)` — carried on BOTH sides.
+     *
+     * DECLARED: from the column definition. LIVE: from introspection, and ONLY when
+     * the dialect materialises a length. An unbounded text family member
+     * (`text`/`longtext`/`mediumtext`/`clob`) leaves this `undefined` rather than
+     * reporting the type's theoretical maximum — mysql answers 4294967295 for
+     * `longtext`, and comparing that against a declared `undefined` would re-emit an
+     * ALTER on every boot forever.
+     *
+     * WHY IT IS HERE AT ALL. It was absent from the snapshot entirely: the value
+     * lived on the column definition, was read only when rendering CREATE DDL, and
+     * never reached the comparison. So the differ was not comparing lengths wrongly
+     * — it could not see them. Adding `.maxLength(n)` to an EXISTING column planned
+     * zero operations and reported "schema is up to date" while the live column
+     * stayed `longtext`. A consumer hit that trying to apply the documented remedy
+     * for MariaDB's hash long-unique, and their contrast is what pinned it: a column
+     * bounded AT CREATION was `varchar(64)` (DDL path, fine), one bounded afterwards
+     * stayed `longtext` (diff path, blind).
+     *
+     * NOT compared on sqlite: it has no length-enforced type, so the declared value
+     * is real and the live side can never report one. Comparing them there would
+     * re-emit forever. See `sameColumnShape`.
+     */
+    readonly maxLength?: number;
     readonly references?: {
         readonly table: string;
         readonly column: string;
@@ -1074,16 +1099,6 @@ export declare interface IndexSnapshot {
     readonly expression?: boolean;
 }
 
-/**
- * Read the current shape of the connected database. Dispatched per
- * dialect; supports postgres only.
- *
- * The returned `SchemaSnapshot` is the same shape `declaredSnapshot`
- * produces — they're directly diffable via `planMigrations`.
- *
- * Restricted to the `public` schema today; multi-schema apps will
- * grow a `schema` parameter when we have a real need.
- */
 export declare const introspectSchema: (sql: SqlClient.SqlClient) => Effect.Effect<SchemaSnapshot, SqlError_2>;
 
 /** Type-guard for the discovery walker. */