note: no summary for this older release
We summarize recent releases. The original release notes for this version are below.
release-notesgithub.com/prisma/orm · 23 lines
- # v8.0.0-rc.7
- ORM collection pagination renames to `limit`/`offset`, and the toolchain releases against `@prisma/cli-engine@0.2.3`, the engine whose config loader ships the `prisma init` scaffold fixes from the unified CLI's rc line.
- The upgrade recipe for this hop: the [user recipe](https://github.com/prisma/prisma/tree/v8.0.0-rc.7/skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.6-to-8.0.0-rc.7/).
- ## Breaking changes
- - **ORM pagination is `limit`/`offset`, not `take`/`skip`** — `.take(n)` and `.skip(n)` are renamed to `.limit(n)` and `.offset(n)` on SQL and Mongo ORM collections, including relation refinements and grouped SQL collections; the old names are removed. Semantics are unchanged. Mongo's lower-level query builder keeps `.skip(n)` — it names the native `$skip` pipeline stage, not the collection API. ([#30112](https://github.com/prisma/prisma/pull/30112))
- Before:
- ```ts
- await db.orm.User.orderBy((u) => u.id.asc()).skip(10).take(10).all();
- ```
- After:
- ```ts
- await db.orm.User.orderBy((u) => u.id.asc()).offset(10).limit(10).all();
- ```
- - **The engine peer moves to `@prisma/cli-engine@0.2.3`** — `@prisma/orm-toolchain` declares the unified CLI's engine as an exact peer, and this release peers 0.2.3 (up from 0.2.2). Installs assembled by the unified `prisma` CLI resolve one engine as before; a host that pins the engine itself must move to 0.2.3. ([prisma/prisma-cli#225](https://github.com/prisma/prisma-cli/pull/225), [prisma/prisma-cli#227](https://github.com/prisma/prisma-cli/pull/227))