@saasicat/adapter-drizzle 1.0.0-rc.22 → 1.0.0-rc.24

package/README.md

@@ -25,6 +25,7 @@ Drizzle schema declares them. It does not create or migrate anything.
 import { Pool } from 'pg';
 import { drizzle } from 'drizzle-orm/node-postgres';
 import { drizzlePersistence } from '@saasicat/adapter-drizzle';
+import { aesGcmSecretSealer } from '@saasicat/nest/platform';
 
 const db = drizzle(new Pool({ connectionString: process.env.DATABASE_URL }));
 
@@ -33,6 +34,8 @@ SaaSiCatModule.forRoot({
     controller: { guards: [JwtAuthGuard] },
     imports: [AuthModule],
     persistence: drizzlePersistence({ db }),
+    // Not the bundle's to supply: the key that seals the SuperAdmin's second factor.
+    adapters: { secretSealer: aesGcmSecretSealer(process.env.SECRET_SEALER_KEY) },
     entitlement: {},
 });
 ```
@@ -40,9 +43,24 @@ SaaSiCatModule.forRoot({
 `drizzlePersistence({ db })` accepts a ready Drizzle database (any pg
 driver — node-postgres, postgres.js) or an injection token, and returns the
 same `SaaSiCatPersistenceAdapter` bundle shape as `prismaPersistence()`.
-Options: `passwordHasher` (enables `core.superAdminProvisioning`) and
-`rlsIntegration` (declares the `rowLevelSecurity` capability once your db
-layer applies the bypass).
+Options: `passwordHasher` (enables `core.superAdminProvisioning`),
+`rlsIntegration` (declares the `rowLevelSecurity` capability — this bundle
+does not lift a row policy itself, unlike the Prisma one; with row policies,
+bind an `RlsBypassPort` of your own in `adapters` that sets the setting your
+policies read inside one transaction), `notAdopted` (the canonical models your schema
+leaves out, as `saasicat schema check` prints them; the bundle leaves out what
+needs them) and `transactions`.
+
+`transactions: { maxConcurrent }` bounds how many of the platform's
+transactions are open at once; the rest wait in arrival order before they
+open. Set it below your pool's `max` — the pool size minus five is a sound
+start — so that the reads a transaction waits on can still get a
+connection. Why, and what is counted, is the same as for
+[`@saasicat/adapter-prisma`](../adapter-prisma/README.md#transactions-under-load).
+How long a transaction or a connection wait may take is the pool's own
+setting (`connectionTimeoutMillis`, `statement_timeout`); the wait for a place
+has none. Every runner on one database handle shares the bound; wired by hand,
+provide the options as `DRIZZLE_TRANSACTION_OPTIONS_TOKEN`.
 
 ## Schema
 
@@ -79,9 +97,10 @@ atomic `claimSlot`/`releaseSlot`/`markExhaustedIfFull` and the slots held for
 checkouts, audit
 write/query/stats, MFA, RLS bypass, SuperAdmin bootstrap
 (`PASSWORD_HASHER_TOKEN`), plan-catalog read/import sinks, the record of the
-applied settings, and the `ZeroPromoRevenueDeductionAggregator` default. Not shipped: contracts,
-bundle bookings, registration, tenant-billing write ports,
-`FirstTimeCustomerCheck` — same as the Prisma adapter.
+applied settings, the maintenance windows, the record of what each subscriber
+was told, and the `ZeroPromoRevenueDeductionAggregator` default.
+Not shipped: registration persistence and `FirstTimeCustomerCheck` — same as the
+Prisma adapter.
 
 Manual wiring binds the db via `DRIZZLE_DB_TOKEN`.
 

package/dist/.build-stamp

@@ -1 +1 @@
-3ff4b63c77f2d88923b4d5dbe1f60bf8d278682c3bde4720da79d759adc4acb8
+7afee47e5b9050bf7f38beec6f0dac14ddb3fe43cbac6c28d15d7619dc94419a