# prisma/release
Prisma v8.0.0-rc.18
importance: highbreakingmigrationfeatureprerelease
This release introduces significant changes to raw SQL handling, middleware hooks, full-text indexing, and polymorphic models. It also includes breaking changes that require careful migration.
affected
Developers using raw SQL in contracts, middleware hooks, full-text indexing, polymorphic models, or SQL ORM client field names are affected.
action
Follow the provided migration recipes and update your codebase to accommodate the breaking changes.
release_signals
-Raw SQL in a contract is a `sql` literal. Quoted strings are refused, and a script is provided to rewrite `.prisma` files.
-Middleware hooks are now activity hooks, with renamed methods and context changes.
-Full-text index is stored as data, not a SQL expression, requiring re-emission of contracts and migration planning.
-Polymorphic base models list variants by discriminator value, requiring contract re-emission.
-SQL ORM client accepts only field names, rejecting column names that differ from field names.
+Raw SQL in a contract is now always a `sql` literal or value.
+Middleware observes each statement and transaction as an activity.
+Full-text index can span several weighted fields and is searched from the ORM by naming it.
migration_steps5 steps
- 01Use the provided app and extension recipes for upgrading from v8.0.0-rc.17 to v8.0.0-rc.18.
- 02Rewrite `.prisma` files to use `sql` literals for raw SQL.
- 03Update middleware hooks to use the new activity-based methods.
- 04Re-emit contracts with full-text indexes and polymorphic models.
- 05Ensure SQL ORM client uses only field names.
code_snippet
```prisma
@@index([email], where: sql`(archived_at IS NULL)`, name: "users_email_active")
```# community_signal
How useful is this release to your stack?
—
net score
Sign in with GitHub to cast your vote.
Sign in with GitHub to vote
You’ll return to this release, then choose your vote.