metal-orm 1.0.6 → 1.0.8

package/README.md

@@ -8,8 +8,8 @@
 
 MetalORM is a TypeScript-first, AST-driven SQL toolkit:
 
-- At the **base level**, it's a clear, deterministic query builder with schema definitions and relation-aware hydration.:contentReference[oaicite:0]{index=0}
-- At the **next level**, it becomes an **ORM runtime** with entities, lazy/batched relations, and a Unit of Work (`OrmContext`) that flushes graph changes in one `saveChanges()`.
+- At the **base level**, it's a clear, deterministic query builder with schema definitions and relation-aware hydration.
+- At the **next level**, it becomes an **ORM runtime** with entities, lazy/batched relations, and a Unit of Work (`OrmContext`) that flushes graph changes in one `saveChanges()`.
 
 Use only the parts you need: query builder + hydration for read-heavy/reporting code, or the full ORM runtime for application/business logic.
 
@@ -17,18 +17,18 @@ Use only the parts you need: query builder + hydration for read-heavy/reporting
 
 ## Documentation
 
-Full docs live in the `docs/` folder:
-
-- [Introduction](docs/index.md)
-- [Getting Started](docs/getting-started.md)
-- [Schema Definition](docs/schema-definition.md)
-- [Query Builder](docs/query-builder.md)
-- [DML Operations](docs/dml-operations.md)
-- [Hydration & Entities](docs/hydration.md)
-- [Runtime & Unit of Work](docs/runtime.md)
-- [Advanced Features](docs/advanced-features.md)
-- [Multi-Dialect Support](docs/multi-dialect-support.md)
-- [API Reference](docs/api-reference.md)
+Full docs live in the `docs/` folder:
+
+- [Introduction](https://github.com/celsowm/metal-orm/blob/main/docs/index.md)
+- [Getting Started](https://github.com/celsowm/metal-orm/blob/main/docs/getting-started.md)
+- [Schema Definition](https://github.com/celsowm/metal-orm/blob/main/docs/schema-definition.md)
+- [Query Builder](https://github.com/celsowm/metal-orm/blob/main/docs/query-builder.md)
+- [DML Operations](https://github.com/celsowm/metal-orm/blob/main/docs/dml-operations.md)
+- [Hydration & Entities](https://github.com/celsowm/metal-orm/blob/main/docs/hydration.md)
+- [Runtime & Unit of Work](https://github.com/celsowm/metal-orm/blob/main/docs/runtime.md)
+- [Advanced Features](https://github.com/celsowm/metal-orm/blob/main/docs/advanced-features.md)
+- [Multi-Dialect Support](https://github.com/celsowm/metal-orm/blob/main/docs/multi-dialect-support.md)
+- [API Reference](https://github.com/celsowm/metal-orm/blob/main/docs/api-reference.md)
 
 ---
 
@@ -36,12 +36,12 @@ Full docs live in the `docs/` folder:
 
 **As a query builder:**
 
-- **Declarative schema definition** with `defineTable`, `col.*`, and typed relations.:contentReference[oaicite:1]{index=1}
-- **Fluent query builder** over a real SQL AST (`SelectQueryBuilder`, `InsertQueryBuilder`, `UpdateQueryBuilder`, `DeleteQueryBuilder`).
-- **Advanced SQL**: CTEs, aggregates, window functions, subqueries, JSON, CASE, EXISTS.
-- **Relation hydration**: turn flat rows into nested objects (`user.posts`, `user.roles`, etc.).:contentReference[oaicite:4]{index=4}
-- **Multi-dialect**: compile once, run on MySQL, PostgreSQL, SQLite, or SQL Server.:contentReference[oaicite:5]{index=5}
-- **DML**: type-safe INSERT / UPDATE / DELETE with `RETURNING` where supported.:contentReference[oaicite:6]{index=6}
+- **Declarative schema definition** with `defineTable`, `col.*`, and typed relations.
+- **Fluent query builder** over a real SQL AST (`SelectQueryBuilder`, `InsertQueryBuilder`, `UpdateQueryBuilder`, `DeleteQueryBuilder`).
+- **Advanced SQL**: CTEs, aggregates, window functions, subqueries, JSON, CASE, EXISTS.
+- **Relation hydration**: turn flat rows into nested objects (`user.posts`, `user.roles`, etc.).
+- **Multi-dialect**: compile once, run on MySQL, PostgreSQL, SQLite, or SQL Server.
+- **DML**: type-safe INSERT / UPDATE / DELETE with `RETURNING` where supported.
 
 **As an ORM runtime (optional):**
 
@@ -62,27 +62,29 @@ npm install metal-orm
 # yarn
 yarn add metal-orm
 
-# pnpm
-pnpm add metal-orm
-
-
-MetalORM compiles SQL; you bring your own driver:
-
-Dialect	Driver	Install
-MySQL / MariaDB	mysql2	npm install mysql2
-SQLite	sqlite3	npm install sqlite3
-PostgreSQL	pg	npm install pg
-SQL Server	tedious	npm install tedious
-
-Pick the matching dialect (MySqlDialect, SQLiteDialect, PostgresDialect, MSSQLDialect) when compiling queries.
-
-README
-
-1. Start simple: tiny table, tiny query
-
-MetalORM can be just a straightforward query builder.
-
-import mysql from 'mysql2/promise';
+# pnpm
+pnpm add metal-orm
+```
+
+MetalORM compiles SQL; you bring your own driver:
+
+| Dialect | Driver | Install |
+| --- | --- | --- |
+| MySQL / MariaDB | `mysql2` | `npm install mysql2` |
+| SQLite | `sqlite3` | `npm install sqlite3` |
+| PostgreSQL | `pg` | `npm install pg` |
+| SQL Server | `tedious` | `npm install tedious` |
+
+Pick the matching dialect (MySqlDialect, SQLiteDialect, PostgresDialect, MSSQLDialect) when compiling queries.
+
+## Quick start
+
+1. Start simple: tiny table, tiny query
+
+MetalORM can be just a straightforward query builder.
+
+```ts
+import mysql from 'mysql2/promise';
 import {
   defineTable,
   col,
@@ -114,22 +116,24 @@ const { sql, params } = listOpenTodos.compile(dialect);
 
 // 4) Run with your favorite driver
 const connection = await mysql.createConnection({ /* ... */ });
-const [rows] = await connection.execute(sql, params);
-
-console.log(rows);
-// [
-//   { id: 1, title: 'Write docs', done: 0 },
-//   { id: 2, title: 'Ship feature', done: 0 },
-// ]
+const [rows] = await connection.execute(sql, params);
+
+console.log(rows);
+// [
+//   { id: 1, title: 'Write docs', done: 0 },
+//   { id: 2, title: 'Ship feature', done: 0 },
+// ]
+```
 
 
 That’s it: schema, query, SQL, done.
 
 2. Relations & hydration: nested results without an ORM
 
-Now let’s add relations and get nested objects, still without committing to a full ORM.
-
-import {
+Now let's add relations and get nested objects, still without committing to a full ORM.
+
+```ts
+import {
   defineTable,
   col,
   hasMany,
@@ -172,41 +176,43 @@ const builder = new SelectQueryBuilder(users)
     columns: [posts.columns.id, posts.columns.title, posts.columns.createdAt],
   }); // eager relation for hydration
 
-const { sql, params } = builder.compile(dialect);
-const [rows] = await connection.execute(sql, params);
-
-// Turn flat rows into nested objects
-const hydrated = hydrateRows(
-  rows as Record<string, unknown>[],
-  builder.getHydrationPlan(),
-);
-
-console.log(hydrated);
-// [
-//   {
-//     id: 1,
-//     name: 'John Doe',
-//     email: 'john@example.com',
-//     postCount: 15,
-//     rank: 1,
-//     posts: [
-//       { id: 101, title: 'Latest Post', createdAt: '2023-05-15T10:00:00Z' },
-//       // ...
-//     ],
-//   },
-//   // ...
-// ]
+const { sql, params } = builder.compile(dialect);
+const [rows] = await connection.execute(sql, params);
+
+// Turn flat rows into nested objects
+const hydrated = hydrateRows(
+  rows as Record<string, unknown>[],
+  builder.getHydrationPlan(),
+);
+
+console.log(hydrated);
+// [
+//   {
+//     id: 1,
+//     name: 'John Doe',
+//     email: 'john@example.com',
+//     postCount: 15,
+//     rank: 1,
+//     posts: [
+//       { id: 101, title: 'Latest Post', createdAt: '2023-05-15T10:00:00Z' },
+//       // ...
+//     ],
+//   },
+//   // ...
+// ]
+```
 
 
 Use this mode anywhere you want powerful SQL + nice nested results, without changing how you manage your models.
 
 3. Turn it up: entities + Unit of Work (ORM mode)
 
-When you’re ready, you can let MetalORM manage entities and relations for you.
-
-Instead of “naked objects”, your queries can return entities attached to an OrmContext:
-
-import {
+When you're ready, you can let MetalORM manage entities and relations for you.
+
+Instead of "naked objects", your queries can return entities attached to an OrmContext:
+
+```ts
+import {
   OrmContext,
   MySqlDialect,
   SelectQueryBuilder,
@@ -251,49 +257,44 @@ const newPost = user.posts.add({ title: 'Hello from ORM mode' });
 // Many-to-many via pivot:
 await user.roles.syncByIds([1, 2, 3]);
 
-// 3) Persist the entire graph
-await ctx.saveChanges();
-// INSERT/UPDATE/DELETE + pivot updates happen in a single Unit of Work.
-
+// 3) Persist the entire graph
+await ctx.saveChanges();
+// INSERT/UPDATE/DELETE + pivot updates happen in a single Unit of Work.
+```
 
-Here’s what the runtime gives you:
 
-Identity map: the same row ↔ the same entity instance within a context.
-
-Change tracking: field writes mark entities as dirty.
-
-Relation tracking: add/remove/sync on relation collections emits relation changes.
-
-Cascades: relation definitions can opt into cascade: 'all' | 'persist' | 'remove' | 'link'.
-
-Single flush: ctx.saveChanges() figures out inserts, updates, deletes, and pivot changes.
+Here's what the runtime gives you:
+
+- Identity map: the same row becomes the same entity instance within a context.
+- Change tracking: field writes mark entities as dirty.
+- Relation tracking: add/remove/sync on relation collections emits relation changes.
+- Cascades: relation definitions can opt into cascade: 'all' | 'persist' | 'remove' | 'link'.
+- Single flush: `ctx.saveChanges()` figures out inserts, updates, deletes, and pivot changes.
 
 You can start your project using only the query builder + hydration and gradually migrate hot paths to entities as you implement the runtime primitives.
 
-When to use which mode?
-
-Query builder + hydration only
-
-Great for reporting, analytics, and places where you already have a model layer.
-
-You keep full control over how objects map to rows.
-
-Entity + Unit of Work runtime
-
-Great for request-scoped application logic and domain modeling.
-
-You want lazy relations, cascades, and less boilerplate around update/delete logic.
-
-Both modes share the same schema, AST, and dialects, so you don't have to pick one forever.
-
-Contributing
-
-Issues and PRs are welcome! If you're interested in pushing the runtime/ORM side further (soft deletes, multi-tenant filters, outbox patterns, etc.), contributions are especially appreciated.
-
-See the Contributing Guide
- for details.
-
-License
-
-MetalORM is MIT licensed
-.
+## When to use which mode?
+
+### Query builder + hydration only
+
+Great for reporting, analytics, and places where you already have a model layer.
+
+You keep full control over how objects map to rows.
+
+### Entity + Unit of Work runtime
+
+Great for request-scoped application logic and domain modeling.
+
+You want lazy relations, cascades, and less boilerplate around update/delete logic.
+
+Both modes share the same schema, AST, and dialects, so you don't have to pick one forever.
+
+## Contributing
+
+Issues and PRs are welcome! If you're interested in pushing the runtime/ORM side further (soft deletes, multi-tenant filters, outbox patterns, etc.), contributions are especially appreciated.
+
+See the contributing guide for details.
+
+## License
+
+MetalORM is MIT licensed.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "metal-orm",
-  "version": "1.0.6",
+  "version": "1.0.8",
   "type": "module",
   "exports": {
     ".": {