@prisma/orm-mongo 8.0.0-rc.17-dev.30 → 8.0.0-rc.17-dev.32

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@prisma/orm-mongo",
-  "version": "8.0.0-rc.17-dev.30",
+  "version": "8.0.0-rc.17-dev.32",
   "license": "Apache-2.0",
   "type": "module",
   "sideEffects": false,
@@ -10,18 +10,18 @@
     "skills"
   ],
   "dependencies": {
-    "@prisma/orm-family-mongo": "8.0.0-rc.17-dev.30",
-    "@prisma/orm-framework": "8.0.0-rc.17-dev.30",
-    "@prisma/orm-target-mongo": "8.0.0-rc.17-dev.30",
-    "@prisma/orm-toolchain": "8.0.0-rc.17-dev.30",
+    "@prisma/orm-family-mongo": "8.0.0-rc.17-dev.32",
+    "@prisma/orm-framework": "8.0.0-rc.17-dev.32",
+    "@prisma/orm-target-mongo": "8.0.0-rc.17-dev.32",
+    "@prisma/orm-toolchain": "8.0.0-rc.17-dev.32",
     "mongodb-connection-string-url": "^7.0.1",
     "pathe": "^2.0.3",
     "tinyglobby": "^0.2.17"
   },
   "devDependencies": {
-    "@internal/mongo": "8.0.0-rc.17-dev.30",
-    "@repo/tsconfig": "8.0.0-rc.17-dev.30",
-    "@repo/tsdown": "8.0.0-rc.17-dev.30",
+    "@internal/mongo": "8.0.0-rc.17-dev.32",
+    "@repo/tsconfig": "8.0.0-rc.17-dev.32",
+    "@repo/tsdown": "8.0.0-rc.17-dev.32",
     "tsdown": "0.22.14",
     "typescript": "5.9.3"
   },

package/skills/prisma-8/SKILL.md

@@ -15,7 +15,7 @@ description: >-
   ORM 7 or earlier (schema.prisma + @prisma/client).
 metadata:
   library: '@prisma/orm-mongo'
-  library_version: '8.0.0-rc.17-dev.30'
+  library_version: '8.0.0-rc.17-dev.32'
   version: '2026-09-12'
 ---
 

package/skills/prisma-8/references/contract.md

@@ -260,6 +260,8 @@ model Feature {
 }
 ```
 
+A variant's base can be in another namespace: write `@@base(ns.Model, "value")`. Such a variant must set `@@map(...)`, because a variant that shares its base's table has to be in the base's namespace.
+
 Verify the polymorphism syntax against the interpreter tests if in doubt: `packages/2-sql/2-authoring/contract-psl/test/interpreter.polymorphism.test.ts`.
 
 Mongo PSL takes the same `@@discriminator(field)` / `@@base(Base, "value")` attributes (the Mongo interpreter implements both; `examples/mongo-demo/src/contract.prisma` declares `Post` with `@@discriminator(kind)` and `Article` / `Tutorial` variants via `@@base(Post, "article")`). Variants share the base's collection — there is no `@@map` on a Mongo variant, since there is no second table to join. The TS builder's `discriminator` option on the model is the programmatic equivalent.
@@ -356,6 +358,46 @@ namespace public {
 
 Canonical worked example: `examples/supabase/src/contract.prisma`.
 
+## Workflow — Mixins (shared members)
+
+The concept: a mixin is a named set of members for one kind of block. Declare it with the block's keyword followed by `mixin`, and include it in a block with `+<Name>`. The emitted contract is the same as if the mixin's members were written at the position of the inclusion.
+
+```prisma
+model mixin Timestamps {
+  createdAt DateTime @default(now())
+  updatedAt DateTime @default(now())
+  @@index([createdAt])
+}
+
+enum mixin BaseRoles {
+  ADMIN = "admin"
+  USER  = "user"
+}
+
+model User {
+  id    Int    @id
+  +Timestamps
+  email String
+}
+
+enum Role {
+  @@type("pg/text@1")
+  +BaseRoles
+  GUEST = "guest"
+}
+```
+
+`User` has the fields `id`, `createdAt`, `updatedAt`, `email`, in that order, and the index on `createdAt`. `Role` has the members `ADMIN`, `USER`, `GUEST`.
+
+Rules:
+
+- **One keyword per mixin.** A `model mixin` can be included only in models, a `type mixin` only in composite types, an `enum mixin` only in enums, and a mixin for a block an extension defines (for example `policy_select mixin`) only in blocks of that keyword.
+- **A member provided twice is an error.** A field name or an enum member that the block already has, from its own body or from another mixin, is reported and the earlier one is kept. Including the same mixin twice in one block is also an error.
+- **A mixin's attributes can name only its own fields.** `@@index([createdAt])` inside `Timestamps` works because `createdAt` is a field of the mixin. An attribute that needs a field of the including model belongs in that model; a model's own attributes can name the fields a mixin provides, as in `@@id([tenantId, id])`.
+- **A mixin cannot include a mixin.**
+- **Names follow namespaces.** A mixin declared in `namespace auth { ... }` is included from another namespace as `+auth.Timestamps`. The types of its fields are looked up from the mixin's namespace, not from the including block's.
+- **A mixin is not a type.** It cannot be used as a field type, and it produces nothing in the contract unless a block includes it.
+
 ## Workflow — Cross-contract foreign keys
 
 The concept: a relation field can reference a model in another contract space using the `<space>:<namespace>.<Model>` form. The contract also supports top-level named-type aliases in a `types {}` block, backed by the same bare type-position constructors used by fields. The `@db.X(args)` channel is removed: rewrite `@db.X` as `X` and `@db.X(args)` as `X(args)`; remaining uses fail with an actionable diagnostic naming the replacement.