@palbase/backend 40.0.3 → 40.0.4

package/dist/bin/palbase-backend.js

@@ -3,7 +3,7 @@ import {
   BootRefused,
   createApp,
   loadConfig
-} from "../chunk-AS2HDWVQ.js";
+} from "../chunk-YORFZMAK.js";
 import "../chunk-RA7KFELX.js";
 import "../chunk-GHNC2UHS.js";
 import "../chunk-XZWOMPD3.js";

package/dist/{chunk-AS2HDWVQ.js → chunk-YORFZMAK.js}

@@ -3824,7 +3824,7 @@ function diagnosingDriver(sql, surface = "service") {
   const original = /* @__PURE__ */ __name((e) => String(e?.message ?? e), "original");
   const explain = /* @__PURE__ */ __name((e) => {
     if (isAbortedTransaction(e)) {
-      return new Error(`This request cannot write any more: an earlier write in it failed, and a request runs in ONE Postgres transaction, so every statement after the failure is refused. Nothing here is retryable in place. Wrap a write you expect to fail in \`Database.$attempt(async (tx) => \u2026)\` \u2014 it takes a SAVEPOINT, so only that write rolls back \u2014 or use \`Database.public.<t>.upsert(data, { onConflict: [...] })\` when the failure you were bracing for is a duplicate row. (${original(e)})`);
+      return new Error(`This request cannot write any more: an earlier write in it failed, and a request runs in ONE Postgres transaction, so every statement after the failure is refused. Nothing here is retryable in place. Wrap a write you expect to fail in \`Database.$attempt(async (tx) => \u2026)\` \u2014 it takes a SAVEPOINT, so only that write rolls back \u2014 or use \`Database.public.<t>.put({ data, onConflict: [...] })\` when the failure you were bracing for is a duplicate row. (${original(e)})`);
     }
     if (isUniqueViolation(e)) {
       return markEngineRaised(new UniqueViolation(constraintOf(e)));
@@ -5594,4 +5594,4 @@ export {
   installEgressFence,
   createApp
 };
-//# sourceMappingURL=chunk-AS2HDWVQ.js.map
+//# sourceMappingURL=chunk-YORFZMAK.js.map