@drzl/validation-core 3.22.0 → 3.22.2

package/README.md

@@ -25,7 +25,8 @@ Shared interfaces and helpers used by validation generators.
 
 - Every dollar speeds up CI hardware and offsets long test runs on my aging laptop.
 - Sponsors get roadmap input and priority responses in GitHub Issues.
-- Prefer a quick overview? Check `docs/sponsor.md` for the current goals and thank-yous.
+- Prefer a quick overview? The current goals and thank-yous are at
+  https://use-drzl.github.io/drzl/sponsor.
 
 ## Exports (essentials)
 

package/dist/index.cjs

@@ -1743,7 +1743,18 @@ var COLUMN_FORMATS = {
   // is refused. A pattern cannot do that arithmetic, and guessing at it turns away working rows.
   // Over 3319 probes against each of a signed and an unsigned column: zero values the server takes
   // and this refuses.
-  mysqlBigint: "^\\s*[+-]?(\\d+(\\.\\d*)?|\\.\\d+)([eE][+-]?\\d*)?\\s*$"
+  mysqlBigint: "^\\s*[+-]?(\\d+(\\.\\d*)?|\\.\\d+)([eE][+-]?\\d*)?\\s*$",
+  // A temporal column carried as text, and the only thing that can be said about one: it is not
+  // blank. Unanchored on purpose, so it means "holds at least one non-whitespace character".
+  //
+  // Everything stronger was refused for the reason the analyzer's `format` comment gives: Postgres
+  // reads 'today', 'January 8, 1999', '01/08/1999' and '20200101' as dates, so a date-shaped
+  // pattern turns away rows the server stores. This one turns away nothing: measured on Postgres,
+  // every temporal type accepts a valid value with surrounding whitespace and refuses '' and ' '
+  // alike, so the set this refuses and the set the server refuses are the same set. The analyzer
+  // decides which columns carry it, per engine and per type, since MySQL's `time` takes a blank
+  // and silently stores 00:00:00.
+  temporalText: "\\S"
 };
 var COERCIBLE_DATE_STRING = "^(?!\\s*[+-])(?!\\s*\\d*\\.?\\d*(?:[eE][+-]?\\d+)?\\s*$)";
 function parsesToADate(expr) {

package/dist/index.js

@@ -1644,7 +1644,18 @@ var COLUMN_FORMATS = {
   // is refused. A pattern cannot do that arithmetic, and guessing at it turns away working rows.
   // Over 3319 probes against each of a signed and an unsigned column: zero values the server takes
   // and this refuses.
-  mysqlBigint: "^\\s*[+-]?(\\d+(\\.\\d*)?|\\.\\d+)([eE][+-]?\\d*)?\\s*$"
+  mysqlBigint: "^\\s*[+-]?(\\d+(\\.\\d*)?|\\.\\d+)([eE][+-]?\\d*)?\\s*$",
+  // A temporal column carried as text, and the only thing that can be said about one: it is not
+  // blank. Unanchored on purpose, so it means "holds at least one non-whitespace character".
+  //
+  // Everything stronger was refused for the reason the analyzer's `format` comment gives: Postgres
+  // reads 'today', 'January 8, 1999', '01/08/1999' and '20200101' as dates, so a date-shaped
+  // pattern turns away rows the server stores. This one turns away nothing: measured on Postgres,
+  // every temporal type accepts a valid value with surrounding whitespace and refuses '' and ' '
+  // alike, so the set this refuses and the set the server refuses are the same set. The analyzer
+  // decides which columns carry it, per engine and per type, since MySQL's `time` takes a blank
+  // and silently stores 00:00:00.
+  temporalText: "\\S"
 };
 var COERCIBLE_DATE_STRING = "^(?!\\s*[+-])(?!\\s*\\d*\\.?\\d*(?:[eE][+-]?\\d+)?\\s*$)";
 function parsesToADate(expr) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@drzl/validation-core",
-  "version": "3.22.0",
+  "version": "3.22.2",
   "private": false,
   "license": "Apache-2.0",
   "type": "module",
@@ -24,7 +24,7 @@
   ],
   "sideEffects": false,
   "dependencies": {
-    "@drzl/analyzer": "^1.21.0"
+    "@drzl/analyzer": "^1.21.2"
   },
   "peerDependencies": {
     "prettier": ">=3"