@drzl/analyzer 1.17.3 → 1.17.4

package/dist/index.cjs

@@ -141,6 +141,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 +254,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 +577,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;
   }
@@ -1235,6 +1248,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

@@ -100,6 +100,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 +213,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 +536,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;
   }
@@ -1194,6 +1207,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.4",
   "private": false,
   "license": "Apache-2.0",
   "type": "module",