Prisma

Today, we are issuing the ninth Beta release: `2.0.0-beta.9` (short: `beta.9`).
Enforcing arrays in `OR`
We used to allow this syntax:
ts
const orIncorrect = await prisma.post.findMany({
orderBy: {
id: 'asc'
},
where: {
OR: {
title: {
equals: "Prisma makes databases easy"
},
authorId: {
equals: 2
}
}
}
});

However, the thing that we want is this:
ts
const orCorrect = await prisma.post.findMany({
orderBy: {
id: 'asc'
},
where: {
OR: [{
title: {
equals: "Prisma makes databases easy"
},
}, {
authorId: {
equals: 2
}
}]
}
})


So only the array syntax makes sense, therefore we also only allow that from now on.

Fixes and improvements
`prisma`

- [Expose a logger interface](https://github.com/prisma/prisma/issues/2204)
- [Emit an error event when the database connection is interrupted](https://github.com/prisma/prisma/issues/2218)
- [Limit implicit m-n relations to primary keys only](https://github.com/prisma/prisma/issues/2262)
- [Rename pinnedPlatform to pinnedBinaryTarget](https://github.com/prisma/prisma/issues/2644)
- [prisma/engine-core forces users to enable esModuleInterop](https://github.com/prisma/prisma/issues/2681)


`prisma-client-js`

- [findMany / OR accepts non-array value - should only accept arrays](https://github.com/prisma/prisma-client-js/issues/657)
- [Queries and mutations stuck (runs forever?) if log option is ['query', 'warn']](https://github.com/prisma/prisma-client-js/issues/714)


`vscode`

- [Ctrl+Space suggests type after type](https://github.com/prisma/vscode/issues/171)
- [suggest `?` after type](https://github.com/prisma/vscode/issues/214)
- [Add JSON to auto-completion types](https://github.com/prisma/vscode/issues/215)


`prisma-engines`

- [Use exact id column type for the version check during introspection](https://github.com/prisma/prisma-engines/issues/772)
- [add `uniqueIndexes` to Model in DMMF](https://github.com/prisma/prisma-engines/issues/787)
- [bring back `default` for Field in DMMF ](https://github.com/prisma/prisma-engines/issues/789)


Credits

Huge thanks to Sytten for helping!

Today, we are issuing the eighth Beta release: `2.0.0-beta.8` (short: `beta.8`).

Breaking change: Splitting `.raw` into `.queryRaw` and `.executeRaw`
When dealing with raw SQL queries, there are two things we care about - the "return payload", which is being calculated by the `SELECT` statement we use and the number of affected rows - if we for example do an `UPDATE` query.

Until now, Prisma Client decided under the hood with a heuristic, when to return the number of affected rows and when to return the result data.
This [heuristic broke](https://github.com/prisma/prisma/issues/2208) if you wanted the opposite of what the heuristic returned.
That means that the decision has to be made by the developer using Prisma Client instead.
Therefore, we **remove the `raw` command** and replace it with `executeRaw` and `queryRaw`.

So what does return what?
- `executeRaw` returns the **number of affected rows**
- `queryRaw` returns the **result data**

The heuristic used to return the data for `SELECT` statements. So if you upgrade to Beta 8, you need to use `queryRaw` for your `SELECT` statements and `executeRaw` for all SQL queries, which mutate data.

The rule of thumb is: Do not use `executeRaw` for queries that return rows.
In Postgres, it will work to use `executeRaw('SELECT 1)`, however, SQLite will not allow that.

Fixes and improvements
`prisma`

- [Make sure Netlify deployments are not listed with their .netlify.com domain in Google and Co](https://github.com/prisma/prisma/issues/1949)
- [.raw doesn't return data if query doesn't start with SELECT statement](https://github.com/prisma/prisma/issues/2208)
- [Prisma 2.0.0-beta.7 `npx prisma generate` issue if working directory contains spaces](https://github.com/prisma/prisma/issues/2612)
- [JSON type is broken for array. Array comes back as `string`.](https://github.com/prisma/prisma/issues/2619)
- [Error: spawn node --max-old-space-size=8096 .\node_modules\prisma\client\generator-build\index.js ENOENT](https://github.com/prisma/prisma/issues/2632)
- [Add a test case for project paths with spaces](https://github.com/prisma/prisma/issues/2636)


`prisma-client-js`

- [Prisma Client removed on adding a new package: Error: prisma/client did not initialize yet](https://github.com/prisma/prisma-client-js/issues/390)
- [JSON types should return a JSON object and not a JavaScript object](https://github.com/prisma/prisma-client-js/issues/691)
- [Datasource override from client constructor doesn't match the datasource block from the schema.prisma file](https://github.com/prisma/prisma-client-js/issues/698)


Credits

Huge thanks to Sytten, merelinguist for helping!

Today, we are issuing the seventh Beta release: `2.0.0-beta.7` (short: `beta.7`).

New Pagination
Prisma Client's pagination has been simplified a lot!

- Removed `first`, `last`, `before`, `after` arguments.
- Added `cursor` and `take` arguments.
- `skip` argument unchanged.

The `take` argument replaces `first` and `last`.
Examples
`first`
js
prisma.user.findMany({
first: 10
})

// becomes
prisma.user.findMany({
take: 10
})


`last`
js
prisma.user.findMany({
last: 10
})

// becomes
prisma.user.findMany({
take: -10
})


`before`
js
prisma.user.findMany({
before: "someid"
first: 10
})

// becomes
prisma.user.findMany({
cursor: "someid"
take: -10
skip: 1
})


`after`
js
prisma.user.findMany({
after: "someid"
first: 10
})

// becomes
prisma.user.findMany({
cursor: "someid"
take: 10
skip: 1
})


The record specified with `cursor` is now included in the results, making `skip: 1` necessary if you want to preserve the previous `before` / `after` semantics.

This diagram illustrates how the pagination works:

cursor: 5
skip: 0 or undefined
│
│
│
▼
┌───┐┌───┐┌───┐┏━━━┓┏━━━┓┌───┐┌───┐┌───┐┌───┐┌───┐
│ 1 ││ 2 ││ 3 │┃ 4 ┃┃ 5 ┃│ 6 ││ 7 ││ 8 ││ 9 ││10 │
└───┘└───┘└───┘┗━━━┛┗━━━┛└───┘└───┘└───┘└───┘└───┘
◀────────
take: -2



cursor: 5
skip: 1
│
│
│
▼
┌───┐┌───┐┏━━━┓┏━━━┓┌───┐┌───┐┌───┐┌───┐┌───┐┌───┐
│ 1 ││ 2 │┃ 3 ┃┃ 4 ┃│ 5 ││ 6 ││ 7 ││ 8 ││ 9 ││10 │
└───┘└───┘┗━━━┛┗━━━┛└───┘└───┘└───┘└───┘└───┘└───┘
◀────────
take: -2



cursor: 5
skip: 2
│
│
│
▼
┌───┐┏━━━┓┏━━━┓┌───┐┌───┐┌───┐┌───┐┌───┐┌───┐┌───┐
│ 1 │┃ 2 ┃┃ 3 ┃│ 4 ││ 5 ││ 6 ││ 7 ││ 8 ││ 9 ││10 │
└───┘┗━━━┛┗━━━┛└───┘└───┘└───┘└───┘└───┘└───┘└───┘
◀────────
take: -2


cursor: 5
skip: 0 or undefined
│
│
│
▼
┌───┐┌───┐┌───┐┌───┐┏━━━┓┏━━━┓┏━━━┓┌───┐┌───┐┌───┐
│ 1 ││ 2 ││ 3 ││ 4 │┃ 5 ┃┃ 6 ┃┃ 7 ┃│ 8 ││ 9 ││10 │
└───┘└───┘└───┘└───┘┗━━━┛┗━━━┛┗━━━┛└───┘└───┘└───┘
──────────▶
take: 3


cursor: 5
skip: 1
│
│
│
▼
┌───┐┌───┐┌───┐┌───┐┌───┐┏━━━┓┏━━━┓┏━━━┓┌───┐┌───┐
│ 1 ││ 2 ││ 3 ││ 4 ││ 5 │┃ 6 ┃┃ 7 ┃┃ 8 ┃│ 9 ││10 │
└───┘└───┘└───┘└───┘└───┘┗━━━┛┗━━━┛┗━━━┛└───┘└───┘
──────────▶
take: 3


cursor: 5
skip: 2
│
│
│
▼
┌───┐┌───┐┌───┐┌───┐┌───┐┌───┐┏━━━┓┏━━━┓┏━━━┓┌───┐
│ 1 ││ 2 ││ 3 ││ 4 ││ 5 ││ 6 │┃ 7 ┃┃ 8 ┃┃ 9 ┃│10 │
└───┘└───┘└───┘└───┘└───┘└───┘┗━━━┛┗━━━┛┗━━━┛└───┘
──────────▶
take: 3


Auto restart on panic
The Query Engine now automatically restarts with an exponential backoff with jitter, if it exits for some reason, for example in the case of a panic. That helps a lot to make Prisma Client more resilient in production!
https://github.com/prisma/prisma/issues/2100

Introspection now recognizes `default(cuid / uuid)`
If you introspect a Prisma 1 schema, the introspection now correctly recognizes `cuid` or `uuid` usage
https://github.com/prisma/prisma/issues/2499

Fixes and improvements
`prisma`

- [Prisma should check for generator binaries in $PATH](https://github.com/prisma/prisma/issues/934)
- [A generator provider should accept arbitrary commands](https://github.com/prisma/prisma/issues/1101)
- [`generate` does not work in folders with spaces](https://github.com/prisma/prisma/issues/1973)
- [Restart engine on panic](https://github.com/prisma/prisma/issues/2100)
- [Unable to save arrays in a Json type field](https://github.com/prisma/prisma/issues/2432)
- [`findMany` with a `select` argument errors out with models with self-relations (sometimes)](https://github.com/prisma/prisma/issues/2442)
- [[Introspection] Identify Prisma 1 Id defaults](https://github.com/prisma/prisma/issues/2499)
- [Prisma Client mixes up DateTimes and IDs when they are `select`ed in queries](https://github.com/prisma/prisma/issues/2501)
- [`findMany` fails to `select` an enum list & a relation scalar at the same time](https://github.com/prisma/prisma/issues/2525)
- [[Prisma Client] Duplicate identifier with models "X" and "XClient"](https://github.com/prisma/prisma/issues/2539)
- [Output notice about Prisma1->Prisma2 upgrade documentation and tool](https://github.com/prisma/prisma/issues/2555)
- [New raw functions not exported from prisma/client](https://github.com/prisma/prisma/issues/2566)
- [Generated GitHub link too long](https://github.com/prisma/prisma/issues/2572)


`prisma-client-js`

- [Error when passing a null value to a nullable Json field type](https://github.com/prisma/prisma-client-js/issues/693)


`vscode`

- [Message: Request textDocument/definition failed with message: Schema parsing](https://github.com/prisma/vscode/issues/144)
- [Show linter snippet in formatting error](https://github.com/prisma/vscode/issues/145)
- [Using svg breaks markeplace publish](https://github.com/prisma/vscode/issues/157)
- [Not possible to use backslash in string field](https://github.com/prisma/vscode/issues/163)
- [Run CI tests every time a release gets published](https://github.com/prisma/vscode/issues/164)
- [Include CLI version in startup output](https://github.com/prisma/vscode/issues/167)
- [Startup output does not include binary hash any more](https://github.com/prisma/vscode/issues/168)
- [Using autocompletion for `default()` puts curcor after `)` instead of inside `()`](https://github.com/prisma/vscode/issues/169)
- [Ctrl+Space does not suggest current model for self relation](https://github.com/prisma/vscode/issues/173)
- [`unique unique`](https://github.com/prisma/vscode/issues/175)
- [Formatter adds new lines on every format call](https://github.com/prisma/vscode/issues/179)
- [Move out anything unimportant to users from README to CONTRUBUTING.md](https://github.com/prisma/vscode/issues/180)
- [Update README preview image](https://github.com/prisma/vscode/issues/181)
- [Improving README](https://github.com/prisma/vscode/issues/182)
- [vscode plugin formatting bug](https://github.com/prisma/vscode/issues/187)
- [Auto-completion for relation directive shows wrong suggestions](https://github.com/prisma/vscode/issues/189)
- [Format incorrectly deletes invalid lines](https://github.com/prisma/vscode/issues/191)
- [Format deletes new lines in invalid block and removes any whitespaces in the beginning](https://github.com/prisma/vscode/issues/192)
- [Format moves lines on every format call in an invalid schema](https://github.com/prisma/vscode/issues/193)


`prisma-engines`

- [Implement simplified pagination](https://github.com/prisma/prisma-engines/issues/762)


Credits

Huge thanks to Sytten, thankwsx, zachasme for helping!

Today, we are issuing the sixth Beta release: `2.0.0-beta.6` (short: `beta.6`).

More powerful `raw` queries with Prisma Client

Thanks to zachasme and Sytten, the `prisma.raw` command became more powerful in https://github.com/prisma/prisma/pull/2311. There are two changes we introduce for `raw`:

Expose `sql-template-tag` helpers

Prisma Client's `raw` mode utilizes the [`sql-template-tag`](https://github.com/blakeembrey/sql-template-tag) library. In order to construct raw SQL queries programmatically, Prisma Client now exposes a few helper functions:

ts
import { sql, empty, join, raw, PrismaClient } from 'prisma/client'

const prisma = new PrismaClient()

const rawQueryTemplateFromSqlTemplate = await prisma.raw(
sql`
SELECT ${join([raw('email'), raw('id'), raw('name')])}
FROM ${raw('User')}
${sql`WHERE name = ${'Alice'}`}
${empty}
`
)


Allowing programmatic positional parameters

Sometimes, a static template string is not enough. Then constructing a string dynamically is the right choice. For this situation, we added support for arbitrary positional parameters:

ts
const result = await prisma.raw(
'SELECT * FROM User WHERE id = $1 OR email = $2;',
1,
'ema.il'
)


Other improvements

- You can now enable pgBouncer in your connection URL by adding the `?pgbouncer=true` parameter (`forceTransactions` from the `PrismaClient` is now deprecated and will be removed in an upcoming release)
- Improved handling of comments in `prisma format`
- Various improvements to Prisma's VS Code extension (e.g. better error messages and debug information)


Fixes and improvements

`prisma`

- [[Introspection] Better `introspect` success message](https://github.com/prisma/prisma/issues/1554)
- [DigitalOcean Postgres + PGBouncer Issues](https://github.com/prisma/prisma/issues/1638)
- [`&sslcert=server-ca.pem` in PostgreSQL connection url throw `Error opening a TLS connection: One or more parameters passed to a function were not valid.`](https://github.com/prisma/prisma/issues/1651)
- [Prisma generate --watch errors](https://github.com/prisma/prisma/issues/1816)
- [Introspect default value with backslashes causes problem when generating client](https://github.com/prisma/prisma/issues/1888)
- [Prisma DMMF parses comments as fields docs](https://github.com/prisma/prisma/issues/1987)
- [Cascade delete does not work unless relation is optional](https://github.com/prisma/prisma/issues/2212)
- [Special-case syntax error for multiple unnamed arguments in directive in the schema parser](https://github.com/prisma/prisma/issues/2317)
- [Error on table update using a mapped field in where clause](https://github.com/prisma/prisma/issues/2329)
- [Add renovate bot for dependencies](https://github.com/prisma/prisma/issues/2334)
- [Prisma Schema: Add .prisma syntax highlighting for Sublime Text](https://github.com/prisma/prisma/issues/2336)
- [Simple filtering for JSON](https://github.com/prisma/prisma/issues/2345)
- [Panic calling findOne with mapped unique key fields](https://github.com/prisma/prisma/issues/2353)
- [Validation issue for schemas with compound foreign keys](https://github.com/prisma/prisma/issues/2387)
- [[introspect] Expose database classification feature](https://github.com/prisma/prisma/issues/2424)
- [If a comment is the last line in a model, `prisma format` will move it out of the model](https://github.com/prisma/prisma/issues/2441)
- [Investigate alternatives to required PgBouncer configuration](https://github.com/prisma/prisma/issues/2453)
- [Overwriting database connection string in `Prisma Client` does not work](https://github.com/prisma/prisma/issues/2510)
- [PgBouncer mode](https://github.com/prisma/prisma/issues/2520)
- [Documentation parsed from doc comment is missing for enums](https://github.com/prisma/prisma/issues/2549)


`prisma-client-js`

- [Document `forceTransactions` / pgBouncer](https://github.com/prisma/prisma-client-js/issues/503)
- [Better instructions on Query Engine panic](https://github.com/prisma/prisma-client-js/issues/610)
- [Ability to use Heroku's pgbouncer](https://github.com/prisma/prisma-client-js/issues/628)
- [Prisma Client failing with PgBouncer Transaction Mode](https://github.com/prisma/prisma-client-js/issues/651)
- [Basic reporting capability for runtime errors in Client ](https://github.com/prisma/prisma-client-js/issues/661)
- [Prisma Client Beta 4 broken with Netlify](https://github.com/prisma/prisma-client-js/issues/672)
- [PANIC error on upsert query](https://github.com/prisma/prisma-client-js/issues/683)
- [Cannot use prisma.create() with nullable field set to null](https://github.com/prisma/prisma-client-js/issues/699)


`vscode`

- [Trailing comments are broken to the next line when formatting](https://github.com/prisma/vscode/issues/3)
- [Recognize Prisma1 schemas and tell user to install the other extension and rename file](https://github.com/prisma/vscode/issues/43)
- [Allow inline comment](https://github.com/prisma/vscode/issues/72)
- [Formatting moves comment from inside model to above model](https://github.com/prisma/vscode/issues/83)
- [Preserve newlines / whitespaces inside models](https://github.com/prisma/vscode/issues/88)
- [Extension deletes unused commented out models](https://github.com/prisma/vscode/issues/89)
- [Use same versioning scheme & release cadence as Prisma itself](https://github.com/prisma/vscode/issues/93)
- [prisma-fmt: add newline in the end of the file](https://github.com/prisma/vscode/issues/97)
- [Triple slash comments in prisma schema file not working](https://github.com/prisma/vscode/issues/104)
- [Versioning scheme](https://github.com/prisma/vscode/issues/121)
- [Add badges and repo explanation to README](https://github.com/prisma/vscode/issues/135)
- [VSCode extension errors when linting .prisma file](https://github.com/prisma/vscode/issues/140)
- [Also output extension name / package and version on startup](https://github.com/prisma/vscode/issues/141)
- [Configuring Git to handle line endings](https://github.com/prisma/vscode/issues/146)
- [Remove Prisma as Icon Theme](https://github.com/prisma/vscode/issues/155)


`prisma-engines`

- [Improve a model's default value in the AST](https://github.com/prisma/prisma-engines/issues/723)


Credits

Huge thanks to Sytten, thankwsx, zachasme for helping!

Today, we are issuing the fifth Beta release: `2.0.0-beta.5` (short: `beta.5`).

Major improvements

Support for Alpine Linux
From now on, you don't need to build your own binaries for Alpine Linux and all musl-based distros anymore. They're [shipped by default](https://github.com/prisma/prisma/issues/702) with the Prisma CLI and Prisma Client.

Support for Node v14
The new Node v14 is from now on [fully supported](https://github.com/prisma/prisma/issues/2361) with the Prisma CLI and Prisma Client.

Fixed issues with JSON support in Prisma Client

You can now use the new `Json` type that was introduced in the last release also in Prisma Client.

Fixes and improvements
`prisma`

- [Provide binaries for Alpine Linux](https://github.com/prisma/prisma/issues/702)
- [Prisma create failing with query interpretation errors](https://github.com/prisma/prisma/issues/2087)
- [Cannot update a column value to null?](https://github.com/prisma/prisma/issues/2324)
- [Add syntax highlighting to more tools](https://github.com/prisma/prisma/issues/2335)
- [Binary targets for FreeBSD in Beta4 no longer working](https://github.com/prisma/prisma/issues/2357)
- [Prisma CLI is throwing segmentation fault with node 14 (fs.writeFileSync arg)](https://github.com/prisma/prisma/issues/2361)


`prisma-client-js`

- [missing FROM-clause entry for table](https://github.com/prisma/prisma-client-js/issues/574)
- [Automatically serialize a non ISO date string if it is serializable by javascript date object](https://github.com/prisma/prisma-client-js/issues/658)
- [Can't create record with Json](https://github.com/prisma/prisma-client-js/issues/680)


`migrate`

- [Bug: Can't save new migration file](https://github.com/prisma/migrate/issues/435)


`vscode`

- [Go To Definition...not going to Definition](https://github.com/prisma/vscode/issues/130)


`prisma-engines`

- [Disallow `null` for certain input types](https://github.com/prisma/prisma-engines/issues/678)
- [Nested create broken](https://github.com/prisma/prisma-engines/issues/721)


Credits

Huge thanks to Sytten for helping!

Today, we are issuing the fourth Beta release: `2.0.0-beta.4` (short: `beta.4`).

Major improvements

Support for JSON types in PostgreSQL and MySQL

Prisma now supports working with JSON data with the new `Json` type in the Prisma data model.

Here's an overview of how it works with different Prisma tools/workflows:

Introspection

The `prisma introspect` command maps the following column types to `Json`:

* Postgres: `JSON` and `JSONB`
* MySQL: `JSON`

Prisma Migrate

`prisma migrate` uses the following data type when creating a column for a field of type `Json`:

* Postgres: `JSONB`
* MySQL: `JSON`

Prisma Client

Fields of type `Json` will be exposed as plain JavaScript objects in the Prisma Client API.

Introducing `prisma format`

From now on, you can run `prisma format` in your project, to make your `schema.prisma` pretty without the VSCode extension 💅

Support for Yarn workspaces

Prisma now [supports Yarn workspaces](https://github.com/prisma/prisma-client-js/issues/664) 🎉

Making Prisma Client generation more robust with `.prisma` folder

The generation of Prisma Client into `node_modules` sometimes caused problems with package managers (e.g. Yarn) which would [occasionally delete the generated code](https://github.com/prisma/prisma-client-js/issues/390).

In order to make the generation more robust, Prisma Client is now generated into a folder called `node_modules/.prisma`. Because of the leading dot in the folder name, package managers do not touch the folder any more. This results in the following folder structure:


node_modules/
↪ .prisma
↪ client
↪ schema.prisma
↪ index.js
↪ index.d.ts
↪ query-engine-darwin
↪ prisma/client (imports the generated code from `.prisma`)


Note that the generated Prisma Client code in `.prisma` is now imported into `prisma/client` which means there is no change for how you import and use Prisma Client in your code! You can still import Prisma Client as before with:

ts
import { PrismaClient } from 'prisma/client'


Open Prisma Studio in specific browser

The `prisma studio --experimental` command now accepts a `--browser` option to let you choose your preferred browser for Prisma Studio, e.g.:


prisma studio --browser "Google Chrome" --experimental


Here's an overview of the browser names you can use per platform (note that double quotes are required when the browser name contains space and the right capitalization is required too):

| OS | Browser | Argument for `--browser` |
| ------- | ------------------- | ----------------------------- |
| Mac OS | Chrome | `"Google Chrome"` |
| | Firefox | `"Firefox"` |
| | Firefox (Developer) | `"Firefox Developer Edition"` |
| | Safari | `"Safari"` |
| Windows | Chrome | `"Google Chrome"` |
| | Firefox | `"Firefox"` |
| | Firefox (Developer) | `"Firefox Developer Edition"` |
| | Brave | `"Brave"` |
| Linux | Chrome | `"google-chrome"` |
| | Firefox | `"firefox"` |
| | Firefox (Developer) | `"firefox-developer-edition"` |
| | Brave | `"brave"` |




Fixes and improvements

`prisma`

- [Data type JSON](https://github.com/prisma/prisma/issues/186)
- [beta.3 (1635) breaks custom binaries (on Alpine)](https://github.com/prisma/prisma/issues/2266)
- [Investigate GCR Panic](https://github.com/prisma/prisma/issues/2242)
- [RUST error, Did not find a relation for model UserDetail and field userid, Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.](https://github.com/prisma/prisma/issues/2214)
- [Difficult to read error report](https://github.com/prisma/prisma/issues/2153)
- [Query by unique constraint missing included properties](https://github.com/prisma/prisma/issues/2141)
- [Update Prisma 1 docs to link to Prisma 2 docs ](https://github.com/prisma/prisma/issues/1948)
- [`introspect` fails on SQLite](https://github.com/prisma/prisma/issues/1648)


`prisma-client-js`

- [Does not work with yarn workspace](https://github.com/prisma/prisma-client-js/issues/664)
- [Type Generation : returned payload type on upsert not using include](https://github.com/prisma/prisma-client-js/issues/660)
- [Providing `null` for a nullable relation results in error](https://github.com/prisma/prisma-client-js/issues/614)
- [Error when setting a relation field to `null`](https://github.com/prisma/prisma-client-js/issues/459)


`migrate`

- [Security issue with dependency - minimist](https://github.com/prisma/migrate/issues/375)
- [cannot drop table because other objects depend on it](https://github.com/prisma/migrate/issues/102)


`vscode`

- [Saving adds random fields to model](https://github.com/prisma/vscode/issues/99)
- [Context-aware auto-completion](https://github.com/prisma/vscode/issues/96)
- [Modelname being formatted as lowercase when auto-creating back relations](https://github.com/prisma/vscode/issues/95)
- [Extension should report failure if formatting / binary execution fails](https://github.com/prisma/vscode/issues/84)
- [Rename "Automatic Publish"](https://github.com/prisma/vscode/issues/82)
- [Show error in VS Code extension when illegal model name is used](https://github.com/prisma/vscode/issues/57)
- [`alpha` version of extension](https://github.com/prisma/vscode/issues/47)
- [Multiple versions (e.g. 0.0.21 and 0.0.22) are missing Git tags](https://github.com/prisma/vscode/issues/46)
- [Clickable Schema (Relations)](https://github.com/prisma/vscode/issues/45)
- [Automated testing](https://github.com/prisma/vscode/issues/33)


Credits

Huge thanks to Sytten for helping!