Prisma: 2.0.0-preview016 Release

Today, we are issuing the sixteenth Preview release: 2.0.0-preview016 (short: preview016).

Note that we recently adjusted the versioning schema in order to fully comply to the semver spec (the first release with the new version schema was 2.0.0-preview014).

Also a huge shoutout to @williamluke4 for his work on this PR: fix(Engine Commands) Pass JSON File to Query Engine 🙌

Major changes

This release contains major improvements to Photon's query engine. The biggest improvement here is that we're lifting the limitation that the query engine is only able to process one request at a time. In practice, this means that the query engine request throughput vastly increases. We see this as a major step towards making Photon.js production-ready! 🎉

Breaking changes

Due to a major refactoring in Lift's migration engine, your migrations are likely going to break if you upgrade to preview016 with an error similar to this: Error parsing the migration steps: Error("unknown field 'name', expected 'model'", line: 1, column: 59).

To get rid of this error, you'll need to manually delete the generated migrations folder from your file system and drop the _Migration table in your database.

Fixes and improvements per Prisma Framework repository

prisma2

• Error While running prisma2 init hello-prisma on macOS mojave
• Do not count .DS_Store as a file to disqualify a folder during prisma2 init with a Starter Kit
• Create architecture diagram for the Prisma Framework internals
• Prisma 2 on Centos 7
• Make Prisma generate independent of environment
• Error: spawn E2BIG
• Remove limitation on 1 request at at time

photonjs

• Filtering null relationships is not possible
• DateTime not converted to Date when using where
• Array types

prisma-engine

• Introspection Engine: test against our collection of database schema examples
• Introspection Engine: Add support for MySQL
• Introspection Engine: extend tests for MySQL
• Introspection Engine: extend tests for Postgres
• Query Engine: Asyncification
• Query Engine: Find a replacement for our current logger (performance)
• Migration Engine: Implement new diffing approach to enable custom types