@volter/world-core 3.0.72 → 3.0.73

package/dist/generated/pack-facts.json

@@ -1726,7 +1726,8 @@
           "database": "world"
         },
         "fill": {
-          "PLANETSCALE_DATABASE_URL": "http_url"
+          "PLANETSCALE_DATABASE_URL": "http_url",
+          "DATABASE_URL": "side:mysql:native_url"
         }
       },
       "prismaAdapter": {
@@ -1734,6 +1735,14 @@
         "export": "PrismaPlanetScale",
         "urlEnv": "PLANETSCALE_DATABASE_URL"
       },
+      "sidePorts": [
+        {
+          "name": "mysql",
+          "option": "wirePort",
+          "flag": "--wire-port",
+          "note": "MySQL's native wire over the same database psdb serves (mysql_native_password, text and prepared statements)"
+        }
+      ],
       "serveExport": "createPlanetscaleTwinServer"
     },
     "polar": {

package/dist/src/managed-database.js

@@ -7,9 +7,9 @@
 // - Nothing here reads the environment, and the tree references none of the rows it writes.
 // - Each batch is ONE transaction sent as ONE extended-protocol pipeline ending in ONE Sync: `BEGIN`, the role
 //   (`SET LOCAL ROLE`), the transaction-local settings (`set_config(…, true)`), the statements and `COMMIT`, every value a
-//   bind parameter. The PGlite host runs a connection's messages up to its Sync under one lock and lets another
-//   connection's read into a session idle inside a transaction; a batch that never sits idle inside its transaction lets
-//   nobody in, so its role and settings reach no other connection.
+//   bind parameter. The PGlite host holds one connection's whole transaction under one lock, readers included, and
+//   native PostgreSQL gives each connection its own session; either way the batch's role and settings reach no other
+//   connection.
 // - The role, which Postgres takes only as SQL text, is quoted as an identifier; which roles a caller may take is the
 //   pack's rule (Supabase's three API roles), checked before a batch is made.
 // - A batch that fails leaves its transaction aborted (the backend skips to the Sync); it is ended with `ROLLBACK` before

package/generated/pack-facts.json

@@ -1726,7 +1726,8 @@
           "database": "world"
         },
         "fill": {
-          "PLANETSCALE_DATABASE_URL": "http_url"
+          "PLANETSCALE_DATABASE_URL": "http_url",
+          "DATABASE_URL": "side:mysql:native_url"
         }
       },
       "prismaAdapter": {
@@ -1734,6 +1735,14 @@
         "export": "PrismaPlanetScale",
         "urlEnv": "PLANETSCALE_DATABASE_URL"
       },
+      "sidePorts": [
+        {
+          "name": "mysql",
+          "option": "wirePort",
+          "flag": "--wire-port",
+          "note": "MySQL's native wire over the same database psdb serves (mysql_native_password, text and prepared statements)"
+        }
+      ],
       "serveExport": "createPlanetscaleTwinServer"
     },
     "polar": {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@volter/world-core",
-  "version": "3.0.72",
+  "version": "3.0.73",
   "description": "The kernel of Volter World: one log per twin, branches as pointers, checkpoints, the fold that keeps a twin current, the head that performs a write against the vendor, references, and the git plane. A twin package builds on it; the runtime serves it.",
   "keywords": [
     "twin",

package/src/managed-database.ts

@@ -7,9 +7,9 @@
 // - Nothing here reads the environment, and the tree references none of the rows it writes.
 // - Each batch is ONE transaction sent as ONE extended-protocol pipeline ending in ONE Sync: `BEGIN`, the role
 //   (`SET LOCAL ROLE`), the transaction-local settings (`set_config(…, true)`), the statements and `COMMIT`, every value a
-//   bind parameter. The PGlite host runs a connection's messages up to its Sync under one lock and lets another
-//   connection's read into a session idle inside a transaction; a batch that never sits idle inside its transaction lets
-//   nobody in, so its role and settings reach no other connection.
+//   bind parameter. The PGlite host holds one connection's whole transaction under one lock, readers included, and
+//   native PostgreSQL gives each connection its own session; either way the batch's role and settings reach no other
+//   connection.
 // - The role, which Postgres takes only as SQL text, is quoted as an identifier; which roles a caller may take is the
 //   pack's rule (Supabase's three API roles), checked before a batch is made.
 // - A batch that fails leaves its transaction aborted (the backend skips to the Sync); it is ended with `ROLLBACK` before