@assemora/database 0.1.0

package/LICENSE

@@ -0,0 +1,202 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Assemora
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.
+

package/README.md

@@ -0,0 +1,163 @@
+# `@assemora/database`
+
+Abstract database adapter contracts and Query AST execution.
+
+**Implementation phase:** 3 — shipped early, in phase 2.
+
+The Query AST (SPEC.md §30) and the adapter contract (SPEC.md §31) live here. They
+are the stable boundary between the data layer, database adapters, the policy layer
+and the AI query layer, and nothing in this package is specific to any engine.
+
+```ts
+const adapter = createMemoryAdapter({ users: [{ id: 'u1', active: true }] })
+
+await adapter.execute(
+  { model: 'users', operation: 'select', where: [comparison('active', '=', true)], order: [], with: [] },
+  { table: usersDescriptor },
+)
+```
+
+The in-memory adapter implements the same contract as `@assemora/database-postgres`,
+so a query proven in a unit test runs unchanged against PostgreSQL. It is for tests
+and development only — nothing it holds is durable.
+
+Every relation kind is loaded in batches, `belongsToMany` included: one pass over the
+join table and one over the target, however many rows are being loaded for, and the
+same again per nested hop. `adapter.diagnostics.scanCount()` counts those passes — one
+per table, the way `statementCount()` counts statements on the PostgreSQL adapter — so
+an N+1 fails a test rather than waiting for a review (SPEC.md §89). What the two
+adapters have to agree the load *means* is settled in
+`tests/integration/adapter-conformance.test.ts` (ADR-0013).
+
+A `belongsToMany` arrives ordered by the target's key, ascending, in both adapters. A
+join table has no order of its own, so without a stated one the same query answers with
+the same rows in different orders and `user.roles[0]` means one thing in a unit test and
+another in production. Every other kind carries whatever order its rows came back in;
+`order` in the Query AST sorts the rows a query selects, not the rows hanging off them.
+
+## Join tables
+
+`belongsToMany` is the one relation that stores nothing on either table it links: the
+pairs live in a third table no model declares (SPEC.md §23). The data layer writes to
+it, the DDL creates it and the diff has to notice it arriving — so it is derived once,
+here, as an ordinary `TableDescriptor`.
+
+```ts
+joinTableDescriptor(User.descriptor, roles, Role.descriptor)
+// name:            'roles_users'
+// columns:         roleId, userId — both required, neither unique on its own
+// uniqueTogether:  [['roleId', 'userId']]
+// relations:       a belongsTo per side, so the table is created with real foreign keys
+```
+
+The name comes from `through` when the relation declares one, and from the two table
+names, sorted, when it does not. The columns are derived the way a `hasMany` foreign
+key is — `users` gives `userId` — and `foreignPivotKey` / `relatedPivotKey` name them
+where that does not fit. Everything is sorted before it is written down, so both
+declarations of a mutual relation describe the *same* table, down to the order of the
+columns: `users.roles` and `roles.users` are one join table, not two that disagree.
+
+A relation whose target is its own table has to name both columns, because `userId`
+twice is not a link; it is refused with an error that says so.
+
+`withJoinTables(tables)` is the schema those tables really have — the declared ones
+plus a join table per `belongsToMany`. It is idempotent, so expanding an expanded
+schema adds nothing.
+
+A model declared for a table a relation derives is **refused**, with an error naming
+the relation and the table. Only the DDL would ever read such a model: the pivot verbs
+of SPEC.md §24 write the two derived columns and nothing else, so a pivot carrying a
+surrogate key or a `joinedAt` is a table `attach` cannot fill, and one carrying exactly
+the two keys is a second descriptor for a name the adapter already builds. A pivot with
+columns of its own is a model like any other — declare it with two `belongsTo`
+relations and address it as an ordinary table, rather than pointing `through` at it.
+
+```ts
+// Refused: `assemora_user_roles` is derived, and `grantedAt` is a column no verb writes.
+roles: belongsToMany(() => Role, { through: 'assemora_user_roles' })
+```
+
+`pivotAddress(owner, relation, row)` is how the data layer addresses the table for one
+row. It answers with the join table, the two column names and the owner's key value —
+enough to write the pivot verbs of SPEC.md §24 as ordinary Query AST, with no
+operation and no adapter method of their own.
+
+```ts
+const pivot = pivotAddress(User.descriptor, roles, user.toJSON(), Role.descriptor)
+
+// attach
+await adapter.execute(
+  {
+    ...emptyQuery(pivot.table.name, 'insert'),
+    data: { [pivot.ownerColumn]: pivot.ownerValue, [pivot.relatedColumn]: roleId },
+  },
+  { table: pivot.table },
+)
+
+// detach
+await adapter.execute(
+  {
+    ...emptyQuery(pivot.table.name, 'delete'),
+    where: [
+      comparison(pivot.ownerColumn, '=', pivot.ownerValue),
+      comparison(pivot.relatedColumn, '=', roleId),
+    ],
+  },
+  { table: pivot.table },
+)
+```
+
+A join table has no key of its own — the pair is its identity — so its `primaryKey` is
+empty and `uniqueTogether` carries the constraint. That is the one thing a generator
+has to read that a model table never sets.
+
+## Schema diffing
+
+`diffSchema(before, after)` says what has to happen for one set of table descriptors
+to become another (SPEC.md §34). It is pure, it holds no SQL and it knows no dialect:
+whether a column can still hold what it held is a property of the types, so the answer
+belongs beside the descriptors every adapter already shares.
+
+```ts
+// Both sides are descriptors the framework produced: the snapshot of the last
+// generated schema, and the model registry as it stands now (ADR-0021).
+const diff = diffSchema(snapshot.tables, declaredTables)
+
+if (isDestructive(diff)) {
+  for (const change of diff.changes) {
+    if (change.destructive) console.warn(describeChange(change)) // "drops column articles.subtitle"
+  }
+}
+```
+
+Both sides are expanded with `withJoinTables` first, so a model that gains a
+`belongsToMany` gains a table in the diff and one that loses it loses the table —
+`db:generate` writes the join table without knowing what a join table is. The
+expansion is idempotent, so a snapshot that already holds one still compares clean.
+
+`SchemaChange` is a discriminated union a generator exhausts with a `switch` and no
+default case, so a new kind of change is a compile error everywhere it has to be
+handled. Every change carries `before`, `after` or both — enough to write the up and
+the down migration without reading the descriptors again — and answers the two risk
+questions `isDestructive` and `mayFailOnExistingRows` ask over the whole diff.
+
+The two questions are different ones. `isDestructive` asks whether applying the diff
+may lose data no later migration can bring back; `mayFailOnExistingRows` asks whether
+a table that already holds rows may refuse it — an `add column ... not null`, a
+narrowing that a stored value does not fit, a unique constraint the rows already
+break. A model default does not answer the second: defaults are applied by the data
+layer on insert and never reach the schema (ADR-0011), so a required column arrives
+with nothing to put in the rows that are already there.
+
+**`introspect()` is not a `before`.** A diff is taken against the generated snapshot
+rather than the live database (ADR-0021), and today it has to be: `introspect()`
+reports `relations: []` and maps an enum column back to the `text` PostgreSQL stores
+it as, so comparing it with the registry reports a foreign key added and a
+`text -> enum` change for every relation and every enum column, on every run. Drift
+against a real database belongs in `assemora db:status`, and needs an introspection
+that reads constraints first.
+
+## Workspace dependencies
+
+- `@assemora/schema`
+- `@assemora/core`

package/dist/adapter.d.ts

@@ -0,0 +1,133 @@
+/**
+ * The database contract (SPEC.md §31).
+ *
+ * Nothing PostgreSQL-specific appears here. `@assemora/database-postgres` implements
+ * these interfaces with Drizzle inside, and no other package ever learns that
+ * (SPEC.md §32, §125.1).
+ */
+import type { AssemoraContext } from '@assemora/core';
+import type { QueryAst } from './query-ast.js';
+export type ColumnType = 'uuid' | 'string' | 'text' | 'integer' | 'bigint' | 'number' | 'decimal' | 'boolean' | 'date' | 'timestamp' | 'json' | 'enum' | 'binary';
+export type ColumnDescriptor = {
+    readonly name: string;
+    readonly type: ColumnType;
+    readonly isPrimary: boolean;
+    readonly isNullable: boolean;
+    readonly isUnique: boolean;
+    readonly isIndexed: boolean;
+    readonly hasDefault: boolean;
+    readonly enumValues?: readonly string[];
+};
+export type RelationKind = 'belongsTo' | 'hasOne' | 'hasMany' | 'belongsToMany';
+export type RelationDescriptor = {
+    readonly name: string;
+    readonly kind: RelationKind;
+    /** The table on the other side. */
+    readonly target: string;
+    /**
+     * The column holding the reference: on this table for `belongsTo`, on the target's
+     * for `hasOne` and `hasMany`. A `belongsToMany` stores no reference on either table
+     * — its two columns live in the join table and are named below.
+     */
+    readonly foreignKey: string;
+    /** The column the reference points at: the owner's key, except for `belongsTo`. */
+    readonly ownerKey: string;
+    /** Join table, for `belongsToMany` only. Derived from the two table names when omitted. */
+    readonly through?: string;
+    /**
+     * The join table column holding this side's key, for `belongsToMany` only.
+     * Derived from this table's name when omitted (`joinTableDescriptor`).
+     */
+    readonly foreignPivotKey?: string;
+    /** The join table column holding the target's key, for `belongsToMany` only. */
+    readonly relatedPivotKey?: string;
+};
+export type TableDescriptor = {
+    readonly name: string;
+    readonly columns: readonly ColumnDescriptor[];
+    /**
+     * The single column that identifies a row, or empty where nothing does. A join
+     * table is identified by its pair of keys, and `uniqueTogether` is what says so.
+     */
+    readonly primaryKey: string;
+    readonly relations: readonly RelationDescriptor[];
+    readonly softDeleteColumn?: string;
+    /**
+     * Groups of columns unique together, one constraint each.
+     *
+     * A different claim from `ColumnDescriptor.isUnique`, which says a column is unique
+     * on its own: a join table's two keys each repeat freely and only the pair may not
+     * (SPEC.md §24).
+     */
+    readonly uniqueTogether?: readonly (readonly string[])[];
+    /**
+     * Whether this table holds one row per language (SPEC.md §131).
+     *
+     * Carried on the descriptor rather than inferred from the presence of a `locale`
+     * column, because a column called `locale` is a perfectly ordinary thing for an
+     * application to declare — a log of what language somebody chose, say — and a read
+     * silently scoped to it would be a filter nobody wrote.
+     */
+    readonly translatable?: boolean;
+    /**
+     * The column a write stamps with the time, where the model declares one.
+     *
+     * Carried like `softDeleteColumn`, and for a reader rather than for a writer: the data
+     * layer already knows which column `timestamp().updated()` made, and this is how a
+     * layer above finds out. It is what makes "this translation is older than the entry it
+     * translates" answerable without a column of its own (SPEC.md §131).
+     */
+    readonly updatedAtColumn?: string;
+};
+/**
+ * The two columns a translatable model carries (SPEC.md §131).
+ *
+ * Named here rather than spelled out in each layer that has to recognise them: the data
+ * layer declares them, the schema diff has to know that a table gaining `locale` is a
+ * table becoming translatable, and the SQL writer has to know what to backfill it with.
+ * Three spellings of one name is how the three come to disagree.
+ */
+export declare const LOCALE_COLUMN = "locale";
+export declare const TRANSLATION_OF_COLUMN = "translationOf";
+/**
+ * What `locale` holds on a row written by a deployment that names no languages.
+ *
+ * A translatable model has to work in an application that serves one language — the
+ * framework ships one, `assemora_pages`, and SPEC.md §9 and §124 both write out the
+ * whole configuration of an application without a word about locales. So the column
+ * cannot demand a code nobody has chosen.
+ *
+ * The empty string says exactly that: this row is in the deployment's own language,
+ * whichever that turns out to be. Which is why a read of the *default* language matches
+ * it too — a page written before a site had languages belongs to the language it was
+ * written in, and that is the default. Without that rule, configuring locales on an
+ * existing project would make every row disappear.
+ */
+export declare const UNSPECIFIED_LOCALE = "";
+export type DatabaseSchema = {
+    readonly tables: readonly TableDescriptor[];
+};
+export type DatabaseContext = {
+    readonly table: TableDescriptor;
+    /** The ambient application context, for logging and auditing (SPEC.md §12). */
+    readonly context?: AssemoraContext;
+    /** Tables the query loads relations from, keyed by table name. */
+    readonly related?: Readonly<Record<string, TableDescriptor>>;
+};
+export type DatabaseAdapter = {
+    /**
+     * Runs a query.
+     *
+     * One failure is part of the contract rather than left to the engine: a query
+     * against a table that has not been created yet must reject with
+     * `schemaNotApplied()` from `./errors.js`, distinct from every other refusal. An
+     * application has to be able to boot against an unapplied schema — that is what
+     * `assemora db:generate` does to read the registry (ADR-0021) — and the boot hook
+     * that survives it may not depend on this package, let alone on an engine, to tell
+     * a missing table from a database that refused it.
+     */
+    execute<T>(query: QueryAst, context: DatabaseContext): Promise<T>;
+    transaction<T>(callback: () => Promise<T>): Promise<T>;
+    introspect(): Promise<DatabaseSchema>;
+};
+//# sourceMappingURL=adapter.d.ts.map

package/dist/adapter.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"adapter.d.ts","sourceRoot":"","sources":["../src/adapter.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AACH,OAAO,KAAK,EAAE,eAAe,EAAE,MAAM,gBAAgB,CAAA;AAErD,OAAO,KAAK,EAAE,QAAQ,EAAE,MAAM,gBAAgB,CAAA;AAE9C,MAAM,MAAM,UAAU,GAClB,MAAM,GACN,QAAQ,GACR,MAAM,GACN,SAAS,GACT,QAAQ,GACR,QAAQ,GACR,SAAS,GACT,SAAS,GACT,MAAM,GACN,WAAW,GACX,MAAM,GACN,MAAM,GACN,QAAQ,CAAA;AAEZ,MAAM,MAAM,gBAAgB,GAAG;IAC7B,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAA;IACrB,QAAQ,CAAC,IAAI,EAAE,UAAU,CAAA;IACzB,QAAQ,CAAC,SAAS,EAAE,OAAO,CAAA;IAC3B,QAAQ,CAAC,UAAU,EAAE,OAAO,CAAA;IAC5B,QAAQ,CAAC,QAAQ,EAAE,OAAO,CAAA;IAC1B,QAAQ,CAAC,SAAS,EAAE,OAAO,CAAA;IAC3B,QAAQ,CAAC,UAAU,EAAE,OAAO,CAAA;IAC5B,QAAQ,CAAC,UAAU,CAAC,EAAE,SAAS,MAAM,EAAE,CAAA;CACxC,CAAA;AAED,MAAM,MAAM,YAAY,GAAG,WAAW,GAAG,QAAQ,GAAG,SAAS,GAAG,eAAe,CAAA;AAE/E,MAAM,MAAM,kBAAkB,GAAG;IAC/B,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAA;IACrB,QAAQ,CAAC,IAAI,EAAE,YAAY,CAAA;IAC3B,mCAAmC;IACnC,QAAQ,CAAC,MAAM,EAAE,MAAM,CAAA;IACvB;;;;OAIG;IACH,QAAQ,CAAC,UAAU,EAAE,MAAM,CAAA;IAC3B,mFAAmF;IACnF,QAAQ,CAAC,QAAQ,EAAE,MAAM,CAAA;IACzB,2FAA2F;IAC3F,QAAQ,CAAC,OAAO,CAAC,EAAE,MAAM,CAAA;IACzB;;;OAGG;IACH,QAAQ,CAAC,eAAe,CAAC,EAAE,MAAM,CAAA;IACjC,gFAAgF;IAChF,QAAQ,CAAC,eAAe,CAAC,EAAE,MAAM,CAAA;CAClC,CAAA;AAED,MAAM,MAAM,eAAe,GAAG;IAC5B,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAA;IACrB,QAAQ,CAAC,OAAO,EAAE,SAAS,gBAAgB,EAAE,CAAA;IAC7C;;;OAGG;IACH,QAAQ,CAAC,UAAU,EAAE,MAAM,CAAA;IAC3B,QAAQ,CAAC,SAAS,EAAE,SAAS,kBAAkB,EAAE,CAAA;IACjD,QAAQ,CAAC,gBAAgB,CAAC,EAAE,MAAM,CAAA;IAClC;;;;;;OAMG;IACH,QAAQ,CAAC,cAAc,CAAC,EAAE,SAAS,CAAC,SAAS,MAAM,EAAE,CAAC,EAAE,CAAA;IACxD;;;;;;;OAOG;IACH,QAAQ,CAAC,YAAY,CAAC,EAAE,OAAO,CAAA;IAC/B;;;;;;;OAOG;IACH,QAAQ,CAAC,eAAe,CAAC,EAAE,MAAM,CAAA;CAClC,CAAA;AAED;;;;;;;GAOG;AACH,eAAO,MAAM,aAAa,WAAW,CAAA;AACrC,eAAO,MAAM,qBAAqB,kBAAkB,CAAA;AAEpD;;;;;;;;;;;;;GAaG;AACH,eAAO,MAAM,kBAAkB,KAAK,CAAA;AAEpC,MAAM,MAAM,cAAc,GAAG;IAC3B,QAAQ,CAAC,MAAM,EAAE,SAAS,eAAe,EAAE,CAAA;CAC5C,CAAA;AAED,MAAM,MAAM,eAAe,GAAG;IAC5B,QAAQ,CAAC,KAAK,EAAE,eAAe,CAAA;IAC/B,+EAA+E;IAC/E,QAAQ,CAAC,OAAO,CAAC,EAAE,eAAe,CAAA;IAClC,kEAAkE;IAClE,QAAQ,CAAC,OAAO,CAAC,EAAE,QAAQ,CAAC,MAAM,CAAC,MAAM,EAAE,eAAe,CAAC,CAAC,CAAA;CAC7D,CAAA;AAED,MAAM,MAAM,eAAe,GAAG;IAC5B;;;;;;;;;;OAUG;IACH,OAAO,CAAC,CAAC,EAAE,KAAK,EAAE,QAAQ,EAAE,OAAO,EAAE,eAAe,GAAG,OAAO,CAAC,CAAC,CAAC,CAAA;IACjE,WAAW,CAAC,CAAC,EAAE,QAAQ,EAAE,MAAM,OAAO,CAAC,CAAC,CAAC,GAAG,OAAO,CAAC,CAAC,CAAC,CAAA;IACtD,UAAU,IAAI,OAAO,CAAC,cAAc,CAAC,CAAA;CACtC,CAAA"}

package/dist/adapter.js

@@ -0,0 +1,26 @@
+/**
+ * The two columns a translatable model carries (SPEC.md §131).
+ *
+ * Named here rather than spelled out in each layer that has to recognise them: the data
+ * layer declares them, the schema diff has to know that a table gaining `locale` is a
+ * table becoming translatable, and the SQL writer has to know what to backfill it with.
+ * Three spellings of one name is how the three come to disagree.
+ */
+export const LOCALE_COLUMN = 'locale';
+export const TRANSLATION_OF_COLUMN = 'translationOf';
+/**
+ * What `locale` holds on a row written by a deployment that names no languages.
+ *
+ * A translatable model has to work in an application that serves one language — the
+ * framework ships one, `assemora_pages`, and SPEC.md §9 and §124 both write out the
+ * whole configuration of an application without a word about locales. So the column
+ * cannot demand a code nobody has chosen.
+ *
+ * The empty string says exactly that: this row is in the deployment's own language,
+ * whichever that turns out to be. Which is why a read of the *default* language matches
+ * it too — a page written before a site had languages belongs to the language it was
+ * written in, and that is the default. Without that rule, configuring locales on an
+ * existing project would make every row disappear.
+ */
+export const UNSPECIFIED_LOCALE = '';
+//# sourceMappingURL=adapter.js.map

package/dist/adapter.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"adapter.js","sourceRoot":"","sources":["../src/adapter.ts"],"names":[],"mappings":"AAqGA;;;;;;;GAOG;AACH,MAAM,CAAC,MAAM,aAAa,GAAG,QAAQ,CAAA;AACrC,MAAM,CAAC,MAAM,qBAAqB,GAAG,eAAe,CAAA;AAEpD;;;;;;;;;;;;;GAaG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAAG,EAAE,CAAA"}

package/dist/errors.d.ts

@@ -0,0 +1,48 @@
+/**
+ * The one database failure a caller above is allowed to survive (SPEC.md §31, §83).
+ *
+ * A unique violation, a bad value, a deadlock: those are things a caller did, and an
+ * adapter reports each of them under a code of its own so the layer above can say
+ * whose mistake it was. This file is for the failure nobody made — the table is not
+ * there yet, because the migrations have not been run.
+ *
+ * It has to be told apart from every other way a database can refuse, because an
+ * application must be able to boot against a schema that is not applied yet: that is
+ * exactly what `assemora db:generate` does when it imports the project's application
+ * to read its registry (ADR-0021), and a boot hook that reads a table would otherwise
+ * need the table its own migration is about to create. "The table does not exist",
+ * "the database refused the connection" and "permission denied" arriving as one code
+ * would make that boot indistinguishable from a broken deployment.
+ *
+ * The distinction lives here rather than in an adapter because it is part of the
+ * adapter *contract*: the caller that survives it is `@assemora/resources`, which may
+ * not learn PostgreSQL to ask the question (SPEC.md §8), and an adapter that reported
+ * a missing table the way it reports a refused connection would make the invariant
+ * unimplementable for everybody above.
+ */
+import { AssemoraError } from '@assemora/core';
+/**
+ * The code every adapter must report a missing table under.
+ *
+ * Exported as a constant because an `AssemoraError` code is a public contract — it
+ * travels to a REST client through `toPayload()` — and a caller too far up the
+ * dependency graph to import this file compares the string instead.
+ */
+export declare const SCHEMA_NOT_APPLIED = "SCHEMA_NOT_APPLIED";
+/**
+ * "This table has not been created yet", with the remedy in the sentence.
+ *
+ * 503 rather than 500: nothing went wrong handling the request, the deployment is
+ * unfinished. It is still an incident — SPEC.md §88 reports everything at 500 and
+ * above — because an application serving in this state answers nothing correctly.
+ */
+export declare const schemaNotApplied: (table: string | undefined, cause?: unknown) => AssemoraError;
+/**
+ * Whether a failure was a missing table and nothing else.
+ *
+ * The one question a boot hook is allowed to ask before carrying on. Everything else
+ * — a refused connection, a database that does not exist, a privilege the user was
+ * never granted — answers `false` here and stops the boot, which is the point.
+ */
+export declare const isSchemaNotApplied: (error: unknown) => error is AssemoraError;
+//# sourceMappingURL=errors.d.ts.map

package/dist/errors.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"errors.d.ts","sourceRoot":"","sources":["../src/errors.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;GAqBG;AACH,OAAO,EAAE,aAAa,EAAE,MAAM,gBAAgB,CAAA;AAE9C;;;;;;GAMG;AACH,eAAO,MAAM,kBAAkB,uBAAuB,CAAA;AAEtD;;;;;;GAMG;AACH,eAAO,MAAM,gBAAgB,UAAW,MAAM,GAAG,SAAS,UAAU,OAAO,KAAG,aAW3E,CAAA;AAEH;;;;;;GAMG;AACH,eAAO,MAAM,kBAAkB,UAAW,OAAO,KAAG,KAAK,IAAI,aACQ,CAAA"}

package/dist/errors.js

@@ -0,0 +1,54 @@
+/**
+ * The one database failure a caller above is allowed to survive (SPEC.md §31, §83).
+ *
+ * A unique violation, a bad value, a deadlock: those are things a caller did, and an
+ * adapter reports each of them under a code of its own so the layer above can say
+ * whose mistake it was. This file is for the failure nobody made — the table is not
+ * there yet, because the migrations have not been run.
+ *
+ * It has to be told apart from every other way a database can refuse, because an
+ * application must be able to boot against a schema that is not applied yet: that is
+ * exactly what `assemora db:generate` does when it imports the project's application
+ * to read its registry (ADR-0021), and a boot hook that reads a table would otherwise
+ * need the table its own migration is about to create. "The table does not exist",
+ * "the database refused the connection" and "permission denied" arriving as one code
+ * would make that boot indistinguishable from a broken deployment.
+ *
+ * The distinction lives here rather than in an adapter because it is part of the
+ * adapter *contract*: the caller that survives it is `@assemora/resources`, which may
+ * not learn PostgreSQL to ask the question (SPEC.md §8), and an adapter that reported
+ * a missing table the way it reports a refused connection would make the invariant
+ * unimplementable for everybody above.
+ */
+import { AssemoraError } from '@assemora/core';
+/**
+ * The code every adapter must report a missing table under.
+ *
+ * Exported as a constant because an `AssemoraError` code is a public contract — it
+ * travels to a REST client through `toPayload()` — and a caller too far up the
+ * dependency graph to import this file compares the string instead.
+ */
+export const SCHEMA_NOT_APPLIED = 'SCHEMA_NOT_APPLIED';
+/**
+ * "This table has not been created yet", with the remedy in the sentence.
+ *
+ * 503 rather than 500: nothing went wrong handling the request, the deployment is
+ * unfinished. It is still an incident — SPEC.md §88 reports everything at 500 and
+ * above — because an application serving in this state answers nothing correctly.
+ */
+export const schemaNotApplied = (table, cause) => new AssemoraError(SCHEMA_NOT_APPLIED, table === undefined
+    ? 'A table this application needs does not exist. Run "assemora db:migrate" to apply the migrations for this project.'
+    : `The table "${table}" does not exist. Run "assemora db:migrate" to apply the migrations for this project.`, {
+    status: 503,
+    ...(table === undefined ? {} : { details: { table } }),
+    cause,
+});
+/**
+ * Whether a failure was a missing table and nothing else.
+ *
+ * The one question a boot hook is allowed to ask before carrying on. Everything else
+ * — a refused connection, a database that does not exist, a privilege the user was
+ * never granted — answers `false` here and stops the boot, which is the point.
+ */
+export const isSchemaNotApplied = (error) => error instanceof AssemoraError && error.code === SCHEMA_NOT_APPLIED;
+//# sourceMappingURL=errors.js.map

package/dist/errors.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"errors.js","sourceRoot":"","sources":["../src/errors.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;GAqBG;AACH,OAAO,EAAE,aAAa,EAAE,MAAM,gBAAgB,CAAA;AAE9C;;;;;;GAMG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAAG,oBAAoB,CAAA;AAEtD;;;;;;GAMG;AACH,MAAM,CAAC,MAAM,gBAAgB,GAAG,CAAC,KAAyB,EAAE,KAAe,EAAiB,EAAE,CAC5F,IAAI,aAAa,CACf,kBAAkB,EAClB,KAAK,KAAK,SAAS;IACjB,CAAC,CAAC,oHAAoH;IACtH,CAAC,CAAC,cAAc,KAAK,uFAAuF,EAC9G;IACE,MAAM,EAAE,GAAG;IACX,GAAG,CAAC,KAAK,KAAK,SAAS,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,EAAE,OAAO,EAAE,EAAE,KAAK,EAAE,EAAE,CAAC;IACtD,KAAK;CACN,CACF,CAAA;AAEH;;;;;;GAMG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAAG,CAAC,KAAc,EAA0B,EAAE,CAC3E,KAAK,YAAY,aAAa,IAAI,KAAK,CAAC,IAAI,KAAK,kBAAkB,CAAA"}