latticesql 4.3.6 → 4.3.7

package/dist/cli.js

@@ -58444,14 +58444,40 @@ async function normalizeEmptyDeletedAt(db) {
     await db.migrate([
       {
         version: `${DELETED_AT_SENTINEL}:all`,
+        // TYPE-AWARE: only a text-like deleted_at column can hold the legacy ''
+        // sentinel. A column that is a real `timestamptz` (some clouds' deleted_at
+        // is) MUST be skipped: the predicate `deleted_at = ''` forces Postgres to
+        // parse `''::timestamptz` at PLAN time — invalid input that throws regardless
+        // of data (a timestamptz column can't even hold ''), which aborted the entire
+        // workspace open. We BLACKLIST the non-text types (timestamp/date/time,
+        // numeric, boolean, json, uuid, bytea, xml) rather than allow-list text — so
+        // text-like columns we don't enumerate (citext, a DOMAIN over text, a custom
+        // text type) are still normalized instead of silently leaving '' rows that
+        // 4.x's `deleted_at IS NULL` predicate would read as DELETED. PER-TABLE FAULT
+        // ISOLATION is the backstop: each table's UPDATE runs in its own
+        // subtransaction, so an exotic type that still errors on `= ''` (enum, inet,
+        // interval, array) — or a blocking trigger/lock — is warned + skipped, never
+        // fatal to the open.
         sql: `DO $LATTICE_DAU$
   DECLARE r record;
 BEGIN
   FOR r IN
     SELECT table_name FROM information_schema.columns
-     WHERE table_schema = current_schema() AND column_name = 'deleted_at'
+     WHERE table_schema = current_schema()
+       AND column_name = 'deleted_at'
+       AND data_type NOT IN (
+         'timestamp with time zone', 'timestamp without time zone',
+         'date', 'time with time zone', 'time without time zone',
+         'integer', 'bigint', 'smallint', 'numeric', 'decimal',
+         'real', 'double precision', 'boolean', 'json', 'jsonb',
+         'bytea', 'uuid', 'xml'
+       )
   LOOP
-    EXECUTE format('UPDATE %I SET deleted_at = NULL WHERE deleted_at = ''''', r.table_name);
+    BEGIN
+      EXECUTE format('UPDATE %I SET deleted_at = NULL WHERE deleted_at = ''''', r.table_name);
+    EXCEPTION WHEN others THEN
+      RAISE WARNING 'lattice: skipped deleted_at normalization for %: %', r.table_name, SQLERRM;
+    END;
   END LOOP;
 END $LATTICE_DAU$;`
       }
@@ -82106,7 +82132,7 @@ function printHelp() {
   );
 }
 function getVersion() {
-  if (true) return "4.3.6";
+  if (true) return "4.3.7";
   try {
     const pkgPath = new URL("../package.json", import.meta.url).pathname;
     const pkg = JSON.parse(readFileSync26(pkgPath, "utf-8"));

package/dist/desktop-entry.js

@@ -58138,14 +58138,40 @@ async function normalizeEmptyDeletedAt(db) {
     await db.migrate([
       {
         version: `${DELETED_AT_SENTINEL}:all`,
+        // TYPE-AWARE: only a text-like deleted_at column can hold the legacy ''
+        // sentinel. A column that is a real `timestamptz` (some clouds' deleted_at
+        // is) MUST be skipped: the predicate `deleted_at = ''` forces Postgres to
+        // parse `''::timestamptz` at PLAN time — invalid input that throws regardless
+        // of data (a timestamptz column can't even hold ''), which aborted the entire
+        // workspace open. We BLACKLIST the non-text types (timestamp/date/time,
+        // numeric, boolean, json, uuid, bytea, xml) rather than allow-list text — so
+        // text-like columns we don't enumerate (citext, a DOMAIN over text, a custom
+        // text type) are still normalized instead of silently leaving '' rows that
+        // 4.x's `deleted_at IS NULL` predicate would read as DELETED. PER-TABLE FAULT
+        // ISOLATION is the backstop: each table's UPDATE runs in its own
+        // subtransaction, so an exotic type that still errors on `= ''` (enum, inet,
+        // interval, array) — or a blocking trigger/lock — is warned + skipped, never
+        // fatal to the open.
         sql: `DO $LATTICE_DAU$
   DECLARE r record;
 BEGIN
   FOR r IN
     SELECT table_name FROM information_schema.columns
-     WHERE table_schema = current_schema() AND column_name = 'deleted_at'
+     WHERE table_schema = current_schema()
+       AND column_name = 'deleted_at'
+       AND data_type NOT IN (
+         'timestamp with time zone', 'timestamp without time zone',
+         'date', 'time with time zone', 'time without time zone',
+         'integer', 'bigint', 'smallint', 'numeric', 'decimal',
+         'real', 'double precision', 'boolean', 'json', 'jsonb',
+         'bytea', 'uuid', 'xml'
+       )
   LOOP
-    EXECUTE format('UPDATE %I SET deleted_at = NULL WHERE deleted_at = ''''', r.table_name);
+    BEGIN
+      EXECUTE format('UPDATE %I SET deleted_at = NULL WHERE deleted_at = ''''', r.table_name);
+    EXCEPTION WHEN others THEN
+      RAISE WARNING 'lattice: skipped deleted_at normalization for %: %', r.table_name, SQLERRM;
+    END;
   END LOOP;
 END $LATTICE_DAU$;`
       }
@@ -81684,7 +81710,7 @@ ${e6.stack ?? ""}`
 }
 
 // src/desktop-entry.ts
-var VERSION2 = true ? "4.3.6" : "unknown";
+var VERSION2 = true ? "4.3.7" : "unknown";
 export {
   VERSION2 as VERSION,
   ensureRootForGui,

package/dist/index.cjs

@@ -62675,14 +62675,40 @@ async function normalizeEmptyDeletedAt(db) {
     await db.migrate([
       {
         version: `${DELETED_AT_SENTINEL}:all`,
+        // TYPE-AWARE: only a text-like deleted_at column can hold the legacy ''
+        // sentinel. A column that is a real `timestamptz` (some clouds' deleted_at
+        // is) MUST be skipped: the predicate `deleted_at = ''` forces Postgres to
+        // parse `''::timestamptz` at PLAN time — invalid input that throws regardless
+        // of data (a timestamptz column can't even hold ''), which aborted the entire
+        // workspace open. We BLACKLIST the non-text types (timestamp/date/time,
+        // numeric, boolean, json, uuid, bytea, xml) rather than allow-list text — so
+        // text-like columns we don't enumerate (citext, a DOMAIN over text, a custom
+        // text type) are still normalized instead of silently leaving '' rows that
+        // 4.x's `deleted_at IS NULL` predicate would read as DELETED. PER-TABLE FAULT
+        // ISOLATION is the backstop: each table's UPDATE runs in its own
+        // subtransaction, so an exotic type that still errors on `= ''` (enum, inet,
+        // interval, array) — or a blocking trigger/lock — is warned + skipped, never
+        // fatal to the open.
         sql: `DO $LATTICE_DAU$
   DECLARE r record;
 BEGIN
   FOR r IN
     SELECT table_name FROM information_schema.columns
-     WHERE table_schema = current_schema() AND column_name = 'deleted_at'
+     WHERE table_schema = current_schema()
+       AND column_name = 'deleted_at'
+       AND data_type NOT IN (
+         'timestamp with time zone', 'timestamp without time zone',
+         'date', 'time with time zone', 'time without time zone',
+         'integer', 'bigint', 'smallint', 'numeric', 'decimal',
+         'real', 'double precision', 'boolean', 'json', 'jsonb',
+         'bytea', 'uuid', 'xml'
+       )
   LOOP
-    EXECUTE format('UPDATE %I SET deleted_at = NULL WHERE deleted_at = ''''', r.table_name);
+    BEGIN
+      EXECUTE format('UPDATE %I SET deleted_at = NULL WHERE deleted_at = ''''', r.table_name);
+    EXCEPTION WHEN others THEN
+      RAISE WARNING 'lattice: skipped deleted_at normalization for %: %', r.table_name, SQLERRM;
+    END;
   END LOOP;
 END $LATTICE_DAU$;`
       }

package/dist/index.js

@@ -62375,14 +62375,40 @@ async function normalizeEmptyDeletedAt(db) {
     await db.migrate([
       {
         version: `${DELETED_AT_SENTINEL}:all`,
+        // TYPE-AWARE: only a text-like deleted_at column can hold the legacy ''
+        // sentinel. A column that is a real `timestamptz` (some clouds' deleted_at
+        // is) MUST be skipped: the predicate `deleted_at = ''` forces Postgres to
+        // parse `''::timestamptz` at PLAN time — invalid input that throws regardless
+        // of data (a timestamptz column can't even hold ''), which aborted the entire
+        // workspace open. We BLACKLIST the non-text types (timestamp/date/time,
+        // numeric, boolean, json, uuid, bytea, xml) rather than allow-list text — so
+        // text-like columns we don't enumerate (citext, a DOMAIN over text, a custom
+        // text type) are still normalized instead of silently leaving '' rows that
+        // 4.x's `deleted_at IS NULL` predicate would read as DELETED. PER-TABLE FAULT
+        // ISOLATION is the backstop: each table's UPDATE runs in its own
+        // subtransaction, so an exotic type that still errors on `= ''` (enum, inet,
+        // interval, array) — or a blocking trigger/lock — is warned + skipped, never
+        // fatal to the open.
         sql: `DO $LATTICE_DAU$
   DECLARE r record;
 BEGIN
   FOR r IN
     SELECT table_name FROM information_schema.columns
-     WHERE table_schema = current_schema() AND column_name = 'deleted_at'
+     WHERE table_schema = current_schema()
+       AND column_name = 'deleted_at'
+       AND data_type NOT IN (
+         'timestamp with time zone', 'timestamp without time zone',
+         'date', 'time with time zone', 'time without time zone',
+         'integer', 'bigint', 'smallint', 'numeric', 'decimal',
+         'real', 'double precision', 'boolean', 'json', 'jsonb',
+         'bytea', 'uuid', 'xml'
+       )
   LOOP
-    EXECUTE format('UPDATE %I SET deleted_at = NULL WHERE deleted_at = ''''', r.table_name);
+    BEGIN
+      EXECUTE format('UPDATE %I SET deleted_at = NULL WHERE deleted_at = ''''', r.table_name);
+    EXCEPTION WHEN others THEN
+      RAISE WARNING 'lattice: skipped deleted_at normalization for %: %', r.table_name, SQLERRM;
+    END;
   END LOOP;
 END $LATTICE_DAU$;`
       }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "latticesql",
-  "version": "4.3.6",
+  "version": "4.3.7",
   "description": "Persistent structured memory for AI agent systems — pluggable SQLite or Postgres backend, LLM context bridge",
   "type": "module",
   "main": "./dist/index.js",