@typesql/postgres 0.2.10 → 0.2.12

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@typesql/postgres",
-  "version": "0.2.10",
+  "version": "0.2.12",
   "description": "postgres.js adapter for TypeSQL.",
   "license": "MIT",
   "repository": {
@@ -28,7 +28,7 @@
     "access": "public"
   },
   "dependencies": {
-    "@typesql/core": "0.8.0"
+    "@typesql/core": "0.9.0"
   },
   "peerDependencies": {
     "postgres": ">=3"

package/CHANGELOG.md

@@ -1,174 +0,0 @@
-# @typesql/postgres
-
-## 0.2.10
-
-### Patch Changes
-
-- Breaking: TypeSQL is split into a dialect-neutral core and a PostgreSQL dialect. `@typesql/core` keeps what dialects share (`createSql`, queries, fragments, executors, row keys, transactions, migrations, the schema markers `Col`, `Nullable`, `Generated`, `View`, … and the type cache) and adds a dialect contract. PostgreSQL moves to `@typesql/core/postgres`: create a `sql` with `createSql<DB>(postgres, executor?)`, import `Json`, `PgCatalog`, `migrations()`, type maps and the function catalog from `@typesql/core/postgres` (which also re-exports the schema markers), and the engine types from `@typesql/core/postgres/engine` (was `@typesql/core/engine`). The Kysely, Drizzle and Prisma packages take the dialect the same way and read the schema from the client's type: `createSql(postgres, db)` (`createSql<DB>(postgres, db)` still picks a schema explicitly). `typesql introspect` and the Prisma generator import the column helpers from `@typesql/core/postgres` by default.
-
-- Updated dependencies:
-  - @typesql/core@0.8.0
-
-## 0.2.9
-
-### Patch Changes
-
-- Validate packages against PostgreSQL behavior and built outputs instead of hand-written test suites.
-
-- Reorganize core internals and remove source comments and inline API documentation without changing SQL behavior.
-
-- Updated dependencies:
-  - @typesql/core@0.7.6
-
-## 0.2.8
-
-### Patch Changes
-
-- Updated dependencies:
-  - @typesql/core@0.7.5
-
-## 0.2.7
-
-### Patch Changes
-
-- Updated dependencies:
-  - @typesql/core@0.7.4
-
-## 0.2.6
-
-### Patch Changes
-
-- Execute sql.prepare() queries with postgres.js prepared statements, including queries without parameters.
-
-- Updated dependencies:
-  - @typesql/core@0.7.3
-
-## 0.2.5
-
-### Patch Changes
-
-- Updated dependencies:
-  - @typesql/core@0.7.2
-
-## 0.2.4
-
-### Patch Changes
-
-- Updated dependencies:
-  - @typesql/core@0.7.1
-
-## 0.2.3
-
-### Patch Changes
-
-- Updated dependencies:
-  - @typesql/core@0.7.0
-
-## 0.2.2
-
-### Patch Changes
-
-- Build and type-check the package with `tsrs`.
-
-- Updated dependencies:
-  - @typesql/core@0.6.1
-
-## 0.2.1
-
-### Patch Changes
-
-- The README is shorter: install, one example and links to the docs site, which now has the details it used to repeat.
-
-- Updated dependencies:
-  - @typesql/core@0.6.0
-
-## 0.2.0
-
-### Minor Changes
-
-- `NoResultError`, `Executor` and `TransactionalSql` are no longer re-exported (from `@typesql/drizzle` also `Sql`, `Query`, `RowType`, `ParamsType`, `DefaultTypeMap` and `TypeMap`); import them from `@typesql/core`.
-
-- `createBigIntSql(sql)` is replaced by `createSql(sql, { bigint: true })`, and `PostgresJsBigIntSql<DB, Keys>` by `PostgresJsSql<DB, Keys, PostgresJsBigIntTypeMap>`.
-
-### Patch Changes
-
-- The README's TypeScript Playground example uses `createSql(sql, { bigint: true })` instead of the removed `createBigIntSql`.
-
-- Updated dependencies:
-  - @typesql/core@0.5.0
-
-## 0.1.5
-
-### Patch Changes
-
-- Updated dependencies:
-  - @typesql/core@0.4.0
-
-## 0.1.4
-
-### Patch Changes
-
-- Updated dependencies:
-  - @typesql/core@0.3.0
-
-## 0.1.3
-
-### Patch Changes
-
-- Updated dependencies:
-  - @typesql/core@0.2.0
-
-## 0.1.2
-
-### Patch Changes
-
-- npm package pages link to the documentation site and the issue tracker, and list keywords.
-
-- READMEs link to an example in the TypeScript Playground.
-
-- Updated dependencies:
-  - @typesql/core@0.1.2
-
-## 0.1.1
-
-### Patch Changes
-
-- Docs, package descriptions and error messages spell the project name TypeSQL.
-
-- Updated dependencies:
-  - @typesql/core@0.1.1
-
-## 0.1.0
-
-### Minor Changes
-
-- Queries run from the `sql` bound to your client: `createSql<DB>(client)` then `sql("…").execute()` (or `executeTakeFirst`, `executeTakeFirstOrThrow`, `executeCount`), and `sql.transaction(async (tx) => …)` for transactions, nested with savepoints; the `query`, `one`, `maybeOne`, `many`, `execute`, `transaction` and `RowCountError` exports of `@typesql/pg` and `@typesql/postgres`, `query` and `execute` of `@typesql/kysely`, and `queryRaw` and `executeRaw` of `@typesql/prisma` are removed.
-
-### Patch Changes
-
-- The README links to the type map tables on the new node-postgres and postgres.js adapter pages of the docs.
-
-- Updated dependencies:
-  - @typesql/core@0.1.0
-
-## 0.0.4
-
-### Patch Changes
-
-- Queries have `executeCount()`, which resolves to the affected row count: an `Executor` may resolve to `{ rows, rowCount }` instead of the rows, as the `executor()` of `@typesql/pg`, `@typesql/postgres` and `@typesql/kysely` now do.
-
-- `execute(db, q)` resolves to 0 instead of `null` for statements without a count, such as DDL, and `PostgresJsRows["count"]` is `number | null`.
-
-- `createSql(executor, { rowKeys: "camelCase" })` (and the adapters' `createSql(client, { rowKeys: "camelCase" })`) camelCases the top-level row keys the way Kysely's `CamelCasePlugin` does, in the row types and in the rows `execute*` and the `query`/`one`/`maybeOne`/`many` helpers return, leaving JSON values untouched.
-
-- The type maps declare what parameters accept (`PgParamTypeMap`, `PostgresJsParamTypeMap`), so `int8`/`numeric` parameters take numbers and bigints and timestamp parameters take strings; postgres.js timestamp parameters also take epoch milliseconds.
-
-- Updated dependencies:
-  - @typesql/core@0.0.4
-
-## 0.0.3
-
-### Patch Changes
-
-- Updated dependencies:
-  - @typesql/core@0.0.3