# Prisma 2.17.0 — Release & Upgrade Intelligence
- **Product:** Prisma (https://prisma.io)
- **Version:** 2.17.0
- **Released:** Feb 16, 2021
- **Impact Score:** 7/10
- **Breaking Changes:** Source flagged
- **Canonical Analysis:** https://changelogs.us/prisma/updates/2.17.0/

## Executive Summary (TL;DR)
Prisma 2.17.0. Source highlight: Today, we are excited to share the `2.17.0` stable release 🎉

## Breaking Changes & Deprecations
- Note that this release comes with some breaking changes. Read the **Breaking changes** section below to learn more.
- Note that this release comes with a few minor breaking changes compared to previous versions. Please read about the **Breaking Changes** below.
- Breaking changes ### Type mapping from Prisma schema to the database for `Float` has changed from `Decimal` to `Double` in MySQL and PostgreSQL
- Breaking changes due to strict type diffing and native types

## New Features
- We've added a new flag `—-force-reset` which first resets the database and then updates the schema - this can be useful to start from scratch and as a way to deal with unexecutable migrations (see above).
- Add `PRISMA_DISABLE_WARNINGS`
- Remove the feature flag for nativeTypes for stabilization, so the native types logic is always active.

## Improvements
- Improvements and changes for `prisma db push`
- `prisma db push` now handles unexecutable migrations better, offering a path forward by resetting the database. For example, adding a new required field without a default value when there are rows in the table is considered an unexecutable migration; in such situations you will be prompted to first reset the database.
- Changes to command options:
- The flag `—-force` has been renamed to `--accept-data-loss` to be more explicit - this is required for certain changes that involve losing data, e.g. dropping a table or dropping a column if there are rows.

## Bug Fixes
- More improvements and bug fixes for Prisma Migrate
- Improvements and bug fixes in Prisma Client
- Prisma Migrate has now a built-in locking functionality to prevent multiple migrations from running concurrently.
- Ensure the Prisma schema is valid before prompting developers to reset the database.
- Better error message when using `migrate dev` - if a non-interactive environment is detected, you'll be suggested to use `prisma migrate deploy` instead.
- Improved error handling when Prisma Migrate finds empty migration directories, e.g. `prisma/migrations/20210119114009_init` (missing `migration.sql` file).

## Upgrade Command
```bash
npm install --save-dev --save-exact prisma@2.17.0
```