@intelligo-dev/core 1.0.0-beta.13 → 1.0.0-beta.14

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@intelligo-dev/core",
-  "version": "1.0.0-beta.13",
+  "version": "1.0.0-beta.14",
   "description": "Database schema, email, logging, notifications, and the conversation, document and identity contracts.",
   "keywords": [
     "intelligo",

package/src/db/migrations/0003_local_payments.sql

@@ -0,0 +1,18 @@
+CREATE TABLE "payments" (
+	"id" text PRIMARY KEY NOT NULL,
+	"provider" text NOT NULL,
+	"invoice_id" text NOT NULL,
+	"workspace_id" text NOT NULL,
+	"user_id" text,
+	"reference" text NOT NULL,
+	"amount_minor" integer NOT NULL,
+	"currency" text NOT NULL,
+	"status" text DEFAULT 'pending' NOT NULL,
+	"fulfilled_at" timestamp,
+	"created_at" timestamp DEFAULT now() NOT NULL,
+	CONSTRAINT "payments_invoice_id_unique" UNIQUE("invoice_id")
+);
+--> statement-breakpoint
+ALTER TABLE "payments" ADD CONSTRAINT "payments_workspace_id_organization_id_fk" FOREIGN KEY ("workspace_id") REFERENCES "public"."organization"("id") ON DELETE cascade ON UPDATE no action;--> statement-breakpoint
+ALTER TABLE "payments" ADD CONSTRAINT "payments_user_id_users_id_fk" FOREIGN KEY ("user_id") REFERENCES "public"."users"("id") ON DELETE set null ON UPDATE no action;--> statement-breakpoint
+CREATE INDEX "payments_workspace_id_idx" ON "payments" USING btree ("workspace_id");

package/src/db/migrations/README.md

@@ -63,8 +63,37 @@ the few places where the old chain and the schema disagreed into line
 created that the framework no longer defines are left untouched; a
 product that still uses them keeps them in its own migrations.
 
-A database that ran only part of the old chain is refused: finish it
-with `@intelligo-dev/core@1.0.0-beta.7` first.
+A database that ran only part of the old chain is refused, and
+`intelligo migrate --check` names the migrations it has not run
+(`legacyMissing` in `--json`). No published version finishes the old
+chain: `@intelligo-dev/core@1.0.0-beta.6`, the last one on npm before the
+baseline, ships it through `0042_sessions_active_organization_id`, and
+the versions that carried `0043_attachments`, `0044_money_micros`,
+`0045_drop_legacy_money_columns` and `0046_user_quotas_per_workspace`
+never reached npm. Their SQL is not in the public repository either:
+its last revision before the baseline, `fdc6c3d`, lists all 48 in the
+journal but carries no `.sql` files. That leaves three ways forward;
+try each on a restored copy first.
+
+1. **You have the missing SQL** — a source checkout of the pre-1.0
+   framework that contains the files. Apply each missing migration in
+   chain order and record it in `drizzle.__drizzle_migrations`: `hash`
+   is the sha256 of the file's contents, which must be the one
+   `legacy-chain.json` lists, and `created_at` its journal `when`. Once
+   the database holds the whole chain, `intelligo migrate` adopts it.
+2. **You do not** — bring the schema to the baseline by hand, then
+   record the baseline as applied the way a push-provisioned database is
+   (next section). Create an empty database, run `intelligo migrate`
+   there, and compare the two schemas (`pg_dump --schema-only`); what
+   differs is what `0043`–`0046` would have done. Mind the data, not
+   only the columns: `0044` backfilled every money amount into
+   `*_micros` columns (MNT at ×1,000,000) with a currency, and `0045`
+   dropped the old `*_mnt` and cents columns only after that copy.
+   Clear the old chain's rows from `drizzle.__drizzle_migrations` and
+   insert the current chain's before the first `intelligo migrate`.
+3. **Start over** — create the database from the baseline and move the
+   rows you keep across. For a deployment whose data is disposable this
+   is the shortest path.
 
 ## Baselining a push-provisioned database
 

package/src/db/migrations/legacy-chain.json

@@ -1,5 +1,5 @@
 {
-  "$comment": "The framework's migration chain before the 1.0 baseline: every entry's tag and the sha256 of its .sql file, as drizzle recorded it in drizzle.__drizzle_migrations. `intelligo migrate` reads it to adopt a database that ran the whole old chain \u2014 it records 0000_baseline as applied without running it. The SQL itself is not shipped.",
+  "$comment": "The framework's migration chain before the 1.0 baseline: every entry's tag and the sha256 of its .sql file, as drizzle recorded it in drizzle.__drizzle_migrations. `intelligo migrate` reads it to adopt a database that ran the whole old chain \u2014 it records 0000_baseline as applied without running it. The SQL itself is not shipped. `alternates`: other hashes the same migration was recorded under \u2014 the SQL npm shipped in 1.0.0-beta.6 differs from the repository's for three of them.",
   "entries": [
     {
       "tag": "0000_sharp_night_nurse",
@@ -151,7 +151,10 @@
     },
     {
       "tag": "0036_executions_audit_jobs",
-      "hash": "8665606757ec96bbd48eaab2b2ebb1ee5b5a86d58ba73635b3229ff94c40e572"
+      "hash": "8665606757ec96bbd48eaab2b2ebb1ee5b5a86d58ba73635b3229ff94c40e572",
+      "alternates": [
+        "c93a93db58737ef13f25138b107711a86f4f21efb48d1c83c18f2ffa07831c3d"
+      ]
     },
     {
       "tag": "0037_rate_limit_minute_bucket",
@@ -159,7 +162,10 @@
     },
     {
       "tag": "0038_user_quotas_generic_usage",
-      "hash": "658b6f64424522d955f2aa4d2ce1fe32b52f0e5adbdba14af75c1678389d7754"
+      "hash": "658b6f64424522d955f2aa4d2ce1fe32b52f0e5adbdba14af75c1678389d7754",
+      "alternates": [
+        "822df887955ddfdb138146ae47612dd0c37c5419b67223b6309b82253efc1c53"
+      ]
     },
     {
       "tag": "0039_platform_admin_impersonation",
@@ -167,7 +173,10 @@
     },
     {
       "tag": "0040_ee_audit_chain",
-      "hash": "16b01fa704f75e13fe85cee307a2dd287e3cbd93e77fd58ce0eb18cc32e178e6"
+      "hash": "16b01fa704f75e13fe85cee307a2dd287e3cbd93e77fd58ce0eb18cc32e178e6",
+      "alternates": [
+        "3a432628f1dcf4c4efbda0421901421fdaaa99c498abdb22ee21c6baef24a005"
+      ]
     },
     {
       "tag": "0041_audit_events_append_only",