Version Packages (next) (#36)

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

Author: github-actions[bot]

.changeset/pre.json

@@ -7,6 +7,7 @@
   "changesets": [
     "effect-v4-beta",
     "insertable-null-and-jointable-fk",
+    "jointable-db-interface-physical-columns",
     "legacy-customtype-detector"
   ]
 }

CHANGELOG.md

@@ -1,5 +1,27 @@
 # Changelog
 
+## 6.0.0-next.3
+
+### Patch Changes
+
+- ff58e31: Fix: implicit M:N join tables now expose their physical `A`/`B` columns in the
+  Kysely `DB` interface.
+
+  Kysely uses `DB`-interface field names as literal SQL column identifiers. The
+  join-table entry was emitted as `Schema.Schema.Type<typeof JoinTable>`, whose
+  keys are the **decoded** semantic names (`product_id`, `product_tag_id`). But an
+  implicit many-to-many table's physical Postgres columns are `A`/`B` (Prisma's
+  convention), so a query like
+  `db.selectFrom('_product_tags').where('_product_tags.product_id', ...)` emitted
+  `WHERE product_id` against a table that only has `A`/`B` → runtime SQL error.
+
+  The join-table `DB` entry is now `Schema.Codec.Encoded<typeof JoinTable>`, whose
+  keys are the **encoded** physical columns `A`/`B` (carrying the branded
+  `columnType` values, so joins remain type-safe against the parent table's branded
+  id). The semantic-name mapping still lives only in the schema's
+  `Schema.encodeKeys`, used when decoding a raw DB row. Regular (non-join) model
+  tables are unchanged (`Schema.Schema.Type<typeof Model>`).
+
 ## 6.0.0-next.2
 
 ### Patch Changes

package.json

@@ -1,6 +1,6 @@
 {
   "name": "prisma-effect-kysely",
-  "version": "6.0.0-next.2",
+  "version": "6.0.0-next.3",
   "description": "Prisma generator that creates Effect Schema types from Prisma schema compatible with Kysely",
   "license": "MIT",
   "author": "Samuel Ho",