@drzl/analyzer 1.17.3 → 1.17.5

package/dist/index.cjs

@@ -87,6 +87,7 @@ var BYTE_STRING_CLASSES = /* @__PURE__ */ new Set([
   "SingleStoreBinary",
   "SingleStoreVarBinary"
 ]);
+var BUFFER_CLASSES = /* @__PURE__ */ new Set(["SQLiteBlobBuffer"]);
 function describeV1Column(column) {
   const codec = column?.codec;
   const dataType = column?.dataType;
@@ -141,6 +142,10 @@ function describeV1Column(column) {
       out.integer = false;
       out.tsType = "number";
       out.dbType = semantic === "float" ? "REAL" : "DOUBLE";
+      if (codec === "float4" || codec === "float8") {
+        out.allowsNaN = true;
+        out.allowsInfinity = true;
+      }
       break;
     }
     case "uuid":
@@ -250,6 +255,10 @@ function describeV1Column(column) {
         out.dbType = "NUMERIC";
         out.integer = false;
         [out.min, out.max] = JS_SAFE_INTEGER_BOUNDS;
+        if (codec === "numeric:number") {
+          out.allowsNaN = true;
+          out.allowsInfinity = false;
+        }
       } else if (js === "string") {
         out.tsType = "string";
         out.dbType = codec === "varchar" ? "VARCHAR" : codec === "char" ? "CHAR" : "TEXT";
@@ -569,6 +578,11 @@ var _SchemaAnalyzer = class _SchemaAnalyzer {
       if (inexact) [out.min, out.max] = inexact;
       out.integer = false;
     }
+    const nonFinite = _SchemaAnalyzer.PG_NON_FINITE[ctor];
+    if (nonFinite) {
+      out.allowsNaN = nonFinite.nan;
+      out.allowsInfinity = nonFinite.infinity;
+    }
     if (/^(Pg)?UUID$/i.test(ctor) || /Uuid$/i.test(ctor)) out.format = "uuid";
     return out;
   }
@@ -580,12 +594,36 @@ var _SchemaAnalyzer = class _SchemaAnalyzer {
           tsType: column?.config?.mode === "timestamp" ? "Date" : "number",
           dbType: "INTEGER"
         };
+      // Both timestamp modes of `integer()`, which are one class and one type. `timestamp` and
+      // `timestamp_ms` differ in the scale of the number on the wire, seconds against
+      // milliseconds, and `mapFromDriverValue` consumes that difference and hands back a `Date`
+      // either way; nothing downstream of the analyzer ever sees the integer. So an arm keyed on
+      // the class covers both, where the mode check that used to answer this fell through the
+      // switch to a default arm testing `config.mode === 'timestamp'` and named only the first.
+      // The second came back `unknown`, and every generator emitted a schema accepting anything.
+      //
+      // `DATE` rather than the `INTEGER` that mode check returned, so the two majors describe the
+      // column identically. `dbType` is read in exactly one place outside this file,
+      // `isIntegerColumn`, which the generators consult only for a `tsType` of `number`, so the
+      // relabel reaches no output. Measured rather than argued: emitting a `Date` column under
+      // both labels, nullable and not, through all five generators gives ten byte-identical pairs.
+      case "SQLiteTimestamp":
+        return { tsType: "Date", dbType: "DATE" };
       case "SQLiteText":
         return { tsType: "string", dbType: "TEXT" };
       case "SQLiteReal":
         return { tsType: "number", dbType: "REAL" };
+      // No 0.4x column is a `SQLiteBlob`: `sqlite-core` builds a `SQLiteBlobBuffer`, a
+      // `SQLiteBlobJson` or a `SQLiteBigInt`, one per mode, and exports no class of this name at
+      // all. The arm answers the hand-built column in sqlite-types.spec.ts and nothing drizzle
+      // produces, which is why a real `blob()` reached neither it nor anything else.
       case "SQLiteBlob":
         return { tsType: "Uint8Array", dbType: "BLOB" };
+      // The class a real `blob()` and `blob({ mode: 'buffer' })` both build. See `BUFFER_CLASSES`
+      // for the measurement; the answers here are v1's own for the same column, so this is the
+      // two majors agreeing rather than a new opinion.
+      case "SQLiteBlobBuffer":
+        return { tsType: "Buffer", dbType: "BYTEA" };
       // SQLite spells a mode as a distinct class rather than as config, so `text({mode:'json'})`
       // is a `SQLiteTextJson` and matched no arm at all: the column came back UNKNOWN, which is
       // wider than the `any` a json column at least used to get.
@@ -867,7 +905,7 @@ var _SchemaAnalyzer = class _SchemaAnalyzer {
       const sqlType = sqlKind.startsWith("MySql") && typeof col?.getSQLType === "function" ? String(col.getSQLType()).toLowerCase() : void 0;
       const byteCap = sqlType ? MYSQL_TEXT_CAPS[sqlType] : void 0;
       const ctorName = String(col?.constructor?.name ?? "");
-      const fallbackShape = dbType === "JSON" || dbType === "JSONB" || col?.config?.mode === "json" ? { kind: "json" } : BYTE_STRING_CLASSES.has(ctorName) ? { kind: "byteString", length: declaredLength(col) } : NUMBER_VECTOR_CLASSES.has(ctorName) ? { kind: "numberVector", length: declaredLength(col) } : BIT_STRING_CLASSES.has(ctorName) ? { kind: "bitstring", length: declaredLength(col), exact: true } : GEOMETRIC_CLASS_SHAPES[ctorName];
+      const fallbackShape = dbType === "JSON" || dbType === "JSONB" || col?.config?.mode === "json" ? { kind: "json" } : BYTE_STRING_CLASSES.has(ctorName) ? { kind: "byteString", length: declaredLength(col) } : BUFFER_CLASSES.has(ctorName) ? { kind: "buffer" } : NUMBER_VECTOR_CLASSES.has(ctorName) ? { kind: "numberVector", length: declaredLength(col) } : BIT_STRING_CLASSES.has(ctorName) ? { kind: "bitstring", length: declaredLength(col), exact: true } : GEOMETRIC_CLASS_SHAPES[ctorName];
       if (fallbackShape?.kind === "byteString") delete constraints.maxLength;
       const shape = (v1?.shape ?? fallbackShape)?.kind;
       const finalTs = v1?.tsType ?? tsType;
@@ -1235,6 +1273,28 @@ _SchemaAnalyzer.INEXACT_RANGES = {
   // column, which Postgres caps far lower: it refuses 2147483648 into a `numeric(10,2)`.
   PgNumericNumber: JS_SAFE_INTEGER_BOUNDS
 };
+/**
+ * The Postgres number columns that hold a non-finite double, and which of the three each holds.
+ *
+ * The class-name half of what `describeV1Column` reads off the codec, and the two must agree: a
+ * fact stated on one path and not the other is a schema that changes when the user upgrades
+ * drizzle, which the cross-major diff in `verify-packed.sh` fails on. These three class names are
+ * the same on both majors, read off real `pgTable` columns on 0.45.2 and on 1.0.0-rc.4, so this
+ * table also answers for a v1 column and the two answers are identical rather than merely
+ * compatible. non-finite-numbers.spec.ts asserts that agreement through the real analyzer.
+ *
+ * Postgres only. No MySQL, SingleStore or SQLite class belongs here: MySQL refuses all three on a
+ * `float`/`double` and stores `0.00` for a `decimal`, and SQLite returns both infinities while
+ * silently turning `NaN` into NULL, which is a different answer that has to arrive whole.
+ *
+ * `PgNumeric` is absent because its value is a string, and its pattern already accepts `NaN` and
+ * `Infinity`. `PgNumericNumber` states `infinity: false` on purpose; see `Column.allowsNaN`.
+ */
+_SchemaAnalyzer.PG_NON_FINITE = {
+  PgReal: { nan: true, infinity: true },
+  PgDoublePrecision: { nan: true, infinity: true },
+  PgNumericNumber: { nan: true, infinity: false }
+};
 var SchemaAnalyzer = _SchemaAnalyzer;
 var index_default = SchemaAnalyzer;
 // Annotate the CommonJS export names for ESM import in node:

package/dist/index.d.cts

@@ -62,6 +62,34 @@ interface Column {
      * generators fall back to the old inference there.
      */
     integer?: boolean;
+    /**
+     * Whether the column stores and returns `NaN`, and whether it does the same for an infinity.
+     *
+     * A range cannot say this. `>=`/`<=` refuses `Infinity` whatever the two numbers are, and `NaN`
+     * compares false against both ends, so a bounded float column described by its range alone
+     * refused three values Postgres stores in it and hands back on SELECT. That is a read-path
+     * defect: every read of such a row fails validation on a column behaving exactly as documented.
+     * The generators render these as a union beside the range rather than as a wider range.
+     *
+     * Measured against PostgreSQL 18.3 through PGlite, on the bound-parameter path a validator
+     * guards. `real` and `double precision` return all three unchanged. An unconstrained `numeric`
+     * does too, but a `numeric(10,2)` refuses either infinity with `22003 numeric field overflow`
+     * while still taking `NaN`, and `integer`/`bigint` refuse all three.
+     *
+     * So `numeric` in `{ mode: 'number' }` states `allowsInfinity: false` deliberately, and it is a
+     * narrowing rather than an oversight: nothing here reads a column's precision or scale, so the
+     * two `numeric` declarations are indistinguishable, and admitting the infinities would make the
+     * schema promise what the server refuses for the commoner of the two.
+     *
+     * Postgres only, today. MySQL refuses all three on a `float`/`double` and silently stores `0.00`
+     * for a `decimal`. SQLite returns both infinities and silently turns `NaN` into NULL, which is
+     * real and is filed on its own: a column needs both halves of that answer or none.
+     *
+     * Absent on every other column, including the string mode of `numeric`, which already carries the
+     * same fact as a pattern; see `COLUMN_FORMATS.numeric` in `@drzl/validation-core`.
+     */
+    allowsNaN?: boolean;
+    allowsInfinity?: boolean;
     /**
      * A string column whose contents have a shape the database enforces.
      *
@@ -451,6 +479,24 @@ declare class SchemaAnalyzer {
      * `number double` on drizzle v1, which is where these pairings come from.
      */
     private static readonly INEXACT_RANGES;
+    /**
+     * The Postgres number columns that hold a non-finite double, and which of the three each holds.
+     *
+     * The class-name half of what `describeV1Column` reads off the codec, and the two must agree: a
+     * fact stated on one path and not the other is a schema that changes when the user upgrades
+     * drizzle, which the cross-major diff in `verify-packed.sh` fails on. These three class names are
+     * the same on both majors, read off real `pgTable` columns on 0.45.2 and on 1.0.0-rc.4, so this
+     * table also answers for a v1 column and the two answers are identical rather than merely
+     * compatible. non-finite-numbers.spec.ts asserts that agreement through the real analyzer.
+     *
+     * Postgres only. No MySQL, SingleStore or SQLite class belongs here: MySQL refuses all three on a
+     * `float`/`double` and stores `0.00` for a `decimal`, and SQLite returns both infinities while
+     * silently turning `NaN` into NULL, which is a different answer that has to arrive whole.
+     *
+     * `PgNumeric` is absent because its value is a string, and its pattern already accepts `NaN` and
+     * `Infinity`. `PgNumericNumber` states `infinity: false` on purpose; see `Column.allowsNaN`.
+     */
+    private static readonly PG_NON_FINITE;
     /**
      * Constraints the column definition already carries, which the analysis used to throw away.
      *

package/dist/index.d.ts

@@ -62,6 +62,34 @@ interface Column {
      * generators fall back to the old inference there.
      */
     integer?: boolean;
+    /**
+     * Whether the column stores and returns `NaN`, and whether it does the same for an infinity.
+     *
+     * A range cannot say this. `>=`/`<=` refuses `Infinity` whatever the two numbers are, and `NaN`
+     * compares false against both ends, so a bounded float column described by its range alone
+     * refused three values Postgres stores in it and hands back on SELECT. That is a read-path
+     * defect: every read of such a row fails validation on a column behaving exactly as documented.
+     * The generators render these as a union beside the range rather than as a wider range.
+     *
+     * Measured against PostgreSQL 18.3 through PGlite, on the bound-parameter path a validator
+     * guards. `real` and `double precision` return all three unchanged. An unconstrained `numeric`
+     * does too, but a `numeric(10,2)` refuses either infinity with `22003 numeric field overflow`
+     * while still taking `NaN`, and `integer`/`bigint` refuse all three.
+     *
+     * So `numeric` in `{ mode: 'number' }` states `allowsInfinity: false` deliberately, and it is a
+     * narrowing rather than an oversight: nothing here reads a column's precision or scale, so the
+     * two `numeric` declarations are indistinguishable, and admitting the infinities would make the
+     * schema promise what the server refuses for the commoner of the two.
+     *
+     * Postgres only, today. MySQL refuses all three on a `float`/`double` and silently stores `0.00`
+     * for a `decimal`. SQLite returns both infinities and silently turns `NaN` into NULL, which is
+     * real and is filed on its own: a column needs both halves of that answer or none.
+     *
+     * Absent on every other column, including the string mode of `numeric`, which already carries the
+     * same fact as a pattern; see `COLUMN_FORMATS.numeric` in `@drzl/validation-core`.
+     */
+    allowsNaN?: boolean;
+    allowsInfinity?: boolean;
     /**
      * A string column whose contents have a shape the database enforces.
      *
@@ -451,6 +479,24 @@ declare class SchemaAnalyzer {
      * `number double` on drizzle v1, which is where these pairings come from.
      */
     private static readonly INEXACT_RANGES;
+    /**
+     * The Postgres number columns that hold a non-finite double, and which of the three each holds.
+     *
+     * The class-name half of what `describeV1Column` reads off the codec, and the two must agree: a
+     * fact stated on one path and not the other is a schema that changes when the user upgrades
+     * drizzle, which the cross-major diff in `verify-packed.sh` fails on. These three class names are
+     * the same on both majors, read off real `pgTable` columns on 0.45.2 and on 1.0.0-rc.4, so this
+     * table also answers for a v1 column and the two answers are identical rather than merely
+     * compatible. non-finite-numbers.spec.ts asserts that agreement through the real analyzer.
+     *
+     * Postgres only. No MySQL, SingleStore or SQLite class belongs here: MySQL refuses all three on a
+     * `float`/`double` and stores `0.00` for a `decimal`, and SQLite returns both infinities while
+     * silently turning `NaN` into NULL, which is a different answer that has to arrive whole.
+     *
+     * `PgNumeric` is absent because its value is a string, and its pattern already accepts `NaN` and
+     * `Infinity`. `PgNumericNumber` states `infinity: false` on purpose; see `Column.allowsNaN`.
+     */
+    private static readonly PG_NON_FINITE;
     /**
      * Constraints the column definition already carries, which the analysis used to throw away.
      *

package/dist/index.js

@@ -46,6 +46,7 @@ var BYTE_STRING_CLASSES = /* @__PURE__ */ new Set([
   "SingleStoreBinary",
   "SingleStoreVarBinary"
 ]);
+var BUFFER_CLASSES = /* @__PURE__ */ new Set(["SQLiteBlobBuffer"]);
 function describeV1Column(column) {
   const codec = column?.codec;
   const dataType = column?.dataType;
@@ -100,6 +101,10 @@ function describeV1Column(column) {
       out.integer = false;
       out.tsType = "number";
       out.dbType = semantic === "float" ? "REAL" : "DOUBLE";
+      if (codec === "float4" || codec === "float8") {
+        out.allowsNaN = true;
+        out.allowsInfinity = true;
+      }
       break;
     }
     case "uuid":
@@ -209,6 +214,10 @@ function describeV1Column(column) {
         out.dbType = "NUMERIC";
         out.integer = false;
         [out.min, out.max] = JS_SAFE_INTEGER_BOUNDS;
+        if (codec === "numeric:number") {
+          out.allowsNaN = true;
+          out.allowsInfinity = false;
+        }
       } else if (js === "string") {
         out.tsType = "string";
         out.dbType = codec === "varchar" ? "VARCHAR" : codec === "char" ? "CHAR" : "TEXT";
@@ -528,6 +537,11 @@ var _SchemaAnalyzer = class _SchemaAnalyzer {
       if (inexact) [out.min, out.max] = inexact;
       out.integer = false;
     }
+    const nonFinite = _SchemaAnalyzer.PG_NON_FINITE[ctor];
+    if (nonFinite) {
+      out.allowsNaN = nonFinite.nan;
+      out.allowsInfinity = nonFinite.infinity;
+    }
     if (/^(Pg)?UUID$/i.test(ctor) || /Uuid$/i.test(ctor)) out.format = "uuid";
     return out;
   }
@@ -539,12 +553,36 @@ var _SchemaAnalyzer = class _SchemaAnalyzer {
           tsType: column?.config?.mode === "timestamp" ? "Date" : "number",
           dbType: "INTEGER"
         };
+      // Both timestamp modes of `integer()`, which are one class and one type. `timestamp` and
+      // `timestamp_ms` differ in the scale of the number on the wire, seconds against
+      // milliseconds, and `mapFromDriverValue` consumes that difference and hands back a `Date`
+      // either way; nothing downstream of the analyzer ever sees the integer. So an arm keyed on
+      // the class covers both, where the mode check that used to answer this fell through the
+      // switch to a default arm testing `config.mode === 'timestamp'` and named only the first.
+      // The second came back `unknown`, and every generator emitted a schema accepting anything.
+      //
+      // `DATE` rather than the `INTEGER` that mode check returned, so the two majors describe the
+      // column identically. `dbType` is read in exactly one place outside this file,
+      // `isIntegerColumn`, which the generators consult only for a `tsType` of `number`, so the
+      // relabel reaches no output. Measured rather than argued: emitting a `Date` column under
+      // both labels, nullable and not, through all five generators gives ten byte-identical pairs.
+      case "SQLiteTimestamp":
+        return { tsType: "Date", dbType: "DATE" };
       case "SQLiteText":
         return { tsType: "string", dbType: "TEXT" };
       case "SQLiteReal":
         return { tsType: "number", dbType: "REAL" };
+      // No 0.4x column is a `SQLiteBlob`: `sqlite-core` builds a `SQLiteBlobBuffer`, a
+      // `SQLiteBlobJson` or a `SQLiteBigInt`, one per mode, and exports no class of this name at
+      // all. The arm answers the hand-built column in sqlite-types.spec.ts and nothing drizzle
+      // produces, which is why a real `blob()` reached neither it nor anything else.
       case "SQLiteBlob":
         return { tsType: "Uint8Array", dbType: "BLOB" };
+      // The class a real `blob()` and `blob({ mode: 'buffer' })` both build. See `BUFFER_CLASSES`
+      // for the measurement; the answers here are v1's own for the same column, so this is the
+      // two majors agreeing rather than a new opinion.
+      case "SQLiteBlobBuffer":
+        return { tsType: "Buffer", dbType: "BYTEA" };
       // SQLite spells a mode as a distinct class rather than as config, so `text({mode:'json'})`
       // is a `SQLiteTextJson` and matched no arm at all: the column came back UNKNOWN, which is
       // wider than the `any` a json column at least used to get.
@@ -826,7 +864,7 @@ var _SchemaAnalyzer = class _SchemaAnalyzer {
       const sqlType = sqlKind.startsWith("MySql") && typeof col?.getSQLType === "function" ? String(col.getSQLType()).toLowerCase() : void 0;
       const byteCap = sqlType ? MYSQL_TEXT_CAPS[sqlType] : void 0;
       const ctorName = String(col?.constructor?.name ?? "");
-      const fallbackShape = dbType === "JSON" || dbType === "JSONB" || col?.config?.mode === "json" ? { kind: "json" } : BYTE_STRING_CLASSES.has(ctorName) ? { kind: "byteString", length: declaredLength(col) } : NUMBER_VECTOR_CLASSES.has(ctorName) ? { kind: "numberVector", length: declaredLength(col) } : BIT_STRING_CLASSES.has(ctorName) ? { kind: "bitstring", length: declaredLength(col), exact: true } : GEOMETRIC_CLASS_SHAPES[ctorName];
+      const fallbackShape = dbType === "JSON" || dbType === "JSONB" || col?.config?.mode === "json" ? { kind: "json" } : BYTE_STRING_CLASSES.has(ctorName) ? { kind: "byteString", length: declaredLength(col) } : BUFFER_CLASSES.has(ctorName) ? { kind: "buffer" } : NUMBER_VECTOR_CLASSES.has(ctorName) ? { kind: "numberVector", length: declaredLength(col) } : BIT_STRING_CLASSES.has(ctorName) ? { kind: "bitstring", length: declaredLength(col), exact: true } : GEOMETRIC_CLASS_SHAPES[ctorName];
       if (fallbackShape?.kind === "byteString") delete constraints.maxLength;
       const shape = (v1?.shape ?? fallbackShape)?.kind;
       const finalTs = v1?.tsType ?? tsType;
@@ -1194,6 +1232,28 @@ _SchemaAnalyzer.INEXACT_RANGES = {
   // column, which Postgres caps far lower: it refuses 2147483648 into a `numeric(10,2)`.
   PgNumericNumber: JS_SAFE_INTEGER_BOUNDS
 };
+/**
+ * The Postgres number columns that hold a non-finite double, and which of the three each holds.
+ *
+ * The class-name half of what `describeV1Column` reads off the codec, and the two must agree: a
+ * fact stated on one path and not the other is a schema that changes when the user upgrades
+ * drizzle, which the cross-major diff in `verify-packed.sh` fails on. These three class names are
+ * the same on both majors, read off real `pgTable` columns on 0.45.2 and on 1.0.0-rc.4, so this
+ * table also answers for a v1 column and the two answers are identical rather than merely
+ * compatible. non-finite-numbers.spec.ts asserts that agreement through the real analyzer.
+ *
+ * Postgres only. No MySQL, SingleStore or SQLite class belongs here: MySQL refuses all three on a
+ * `float`/`double` and stores `0.00` for a `decimal`, and SQLite returns both infinities while
+ * silently turning `NaN` into NULL, which is a different answer that has to arrive whole.
+ *
+ * `PgNumeric` is absent because its value is a string, and its pattern already accepts `NaN` and
+ * `Infinity`. `PgNumericNumber` states `infinity: false` on purpose; see `Column.allowsNaN`.
+ */
+_SchemaAnalyzer.PG_NON_FINITE = {
+  PgReal: { nan: true, infinity: true },
+  PgDoublePrecision: { nan: true, infinity: true },
+  PgNumericNumber: { nan: true, infinity: false }
+};
 var SchemaAnalyzer = _SchemaAnalyzer;
 var index_default = SchemaAnalyzer;
 export {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@drzl/analyzer",
-  "version": "1.17.3",
+  "version": "1.17.5",
   "private": false,
   "license": "Apache-2.0",
   "type": "module",