2.0.0-preview-13

Today, we are issuing the thirteenth Preview release: 2.0.0-preview-13 (short: preview-13).

Note: Due to a German holiday, there won't be a Prisma 2 release next week. The next release 2.0.0-preview-14 will happen in two weeks, on Thursday (October 10th).

A special shoutout to @wardpeet whose PR fixed Photon's query engine on Windows 🙏

Breaking changes

This version contains a breaking change in the _Migrations table that Lift uses to store the migration history of a project.

Due to that change, you might encounter an error looking similar to this:

thread 'tokio-runtime-worker-0' panicked at 'Deserializing the database migration failed.: 
Error("missing field `original_steps`", line: 0, column: 0)', src/libcore/result.rs:999:5

If you see that error, you need to manually delete the _Migration table from your database as a workaround.

Major changes

Prisma Studio is getting more stable! We were able to fix a number of bugs that impacted the experience when using Studio. Be sure to try the new Studio version out by entering Prisma's development mode with prisma2 dev and open the provided Studio endpoint in your browser. You can report Studio bugs here.

Another improvement that comes with this release enables you to directly submit detailed error reports whenever the Lift CLI crashes. There won't be any cryptic Rust stracktraces any more in the terminal, instead you'll be shown a dialogue where you can confirm the error report submission.

Fixes and improvements per Prisma 2 repository

prisma2

• Limitations: Missing out of scope, Details for Custom Types
• Document the HTTP proxy feature
• Installation of prisma2 behind corporate proxy
• Init flow with Postgres - schema off by one
• prisma2 init does not find ts-node when using starter kit "GraphQL API (+ Auth)"
• Can't select Just the Prisma schema option in Blank project flow during prisma2 init
• Clarify when/whether limitations are expected to be resolved
• Temporary error telemetry flow in CLI

photonjs

• Nested reads
• Loose connection with MySQL

lift

• Unexpected token. when running prisma2 lift save after adding custom type definition

studio

• Focus first cell when creating a row
• Automatically increase pagination count after committing a create action
• Sidebar improvements
• Tabs button is off
• UI Regression: Improve design when prisma dev has stopped running
• Selected cell: Hitting enter should make cell editable
• Databrowser: Adjust visual state when record is selected
• Cell editing design is off
• Editing boolean cell should directly open dropdown

prisma-engine

• Datamodel Parser: Multi field unique

2.0.0-preview-12

Today, we are issuing the twelfth Preview release: 2.0.0-preview-12 (short: preview-12).

Breaking changes

We have adjusted the way how the Photon constructor is exported from @generated/photon, it's not a default export any more. Therefore, it now needs to be imported as follows:

import { Photon } from '@generated/photon'
// or
const { Photon } = require('@generated/photon')

The previous import syntax is not valid any more:

import Photon from '@generated/photon'
// or
const Photon = require('@generated/photon')

Major changes

In previous versions, when running prisma2 lift save against a database that didn't exist, Lift would always create this database on your PostgreSQL or MySQL database server without further notice.

This could lead to confusion, e.g. when there is a typo in the database name. In that case, Lift would create the database with the wrong name. preview-12 now includes an extra validation step that asks explicitly if the database should be created. You can skip the prompt using the new --create-db flag, e.g. prisma2 lift save --create-db.

Fixes and improvements per Prisma 2 repository

prisma2

• Project bootstrapped by the init flow should use the latest version of prisma2
• Migration Engine: Add canConnect RPC

photonjs

• Generated typings are not working properly with JavaScript

lift

• Remove database create logic inside lift, fail fast if the database doesn't exist.

2.0.0-preview-11

Today, we are issuing the eleventh Preview release: 2.0.0-preview-11 (short: preview-11).

Major changes

For this release, we have invested a lot into fixing bugs across the stack.
Worth pointing out: We worked on the initial support for Windows. Please try it out, if you have Windows!

Try it yourself by upgrading to the latest version:

npm install -g prisma2

Please share your feedback and report any issues you might encounter!

Fixes and improvements per Prisma 2 repository

prisma2

• [Windows] prisma2 init endless spinner
• [Windows] prisma2 init Error during command execution
• [Windows] npm install -g prisma2 with failing command
• prisma2 dev doesn't generate
• CLI + Photon: Download and use Windows binary
• Update documentation to not contain not yet implemented functionality
• Temporary error telemetry docs
• Lift and Photon search for database in different folders
• Upload introspection engine binary to S3

photonjs

• Sqlite path can't be ovewritten
• Missing documentation property in DMMF.Field and DMMF.Model
• "Field does not exist on enclosing type" when using notIn

studio

• Disable expanding loading fields
• Weird scrolling bug when using code queries
• Pagination is broken
• Code snippet lost after reloading/reopening
• Clicking outside the editable cell should unselect it
• Error message: Weird stacktrace encoding
• isDirty Error on Studio
• How does limbo affect tabs?
• Always centered new tab dropdown
• Tree view: Add loading indicator (and other improvements)
• Tree view: Error when expanding an empty list
• Add "Reload" button + report issue flow
• Add ability to open the same script in multiple tabs
• Project selector on Electron needs to be scrollable on smaller screens
• Design idea: Apply "type icons" from tree view to table header
• Preview Tabs

lift

• @unique does not work for columns using @map
• Windows database_migration datamodel_steps too small
• Lift overshoots with the database steps
• Error running Lift on Windows

prisma-engine

• Clean up internal introspection naming
• Upload introspection engine binary to S3

2.0.0-preview-10

Today, we are issuing the tenth Preview release: 2.0.0-preview-10 (short: preview-10).

Major changes

For this release, we have invested a lot into fixing bugs across the stack. Prisma Studio got many fixes and you should check that out.

Try it yourself by upgrading to the latest version:

npm install -g prisma2

Please share your feedback and report any issues you might encounter.

Fixes and improvements per Prisma 2 repository

prisma2

• Minor UI issue with init flow
• Blank project selection in prisma2 init flow ends on hanging No example selected message
• Examples and Docs should not use both @id and @unique
• Missing credentials in Postgres URL: Got invalid RPC response without .result property

studio

• Enums are not rendered
• Arrow-button on the bottom-left doesn't make the sidebar stick
• Horizontal scrolling bug
• Very slow for larger collections
• Manage orphaned sessions
• Designs for when you try to close a dirty tab

prisma-engine

• Build a prototype to compare performance of synchronous and asynchronous database drivers

2.0.0-preview-9.1

Fixes

This release includes an important fix for the init flow, which ended up hanging with specific settings when downloading an example.

We also fixed an edge-case where you could get into an empty state #467

2.0.0-preview-9

Today, we are issuing the ninth Preview release: 2.0.0-preview-9 (short: preview-9).

Major changes

For this release, we have invested a lot into making the prisma2 init command a lot more approachable and user-friendly. The wizard that's launched by prisma2 init helps you to set up a new project. With this release, the wizard becomes a lot more robust and provides a clearer user flows than before.

Try it yourself by upgrading to the latest version and using the init command:

npm install -g prisma2
prisma2 init hello-world

Please share your feedback for the init flow and report any issues you might encounter.

Fixes and improvements per Prisma 2 repository

prisma2

• Prisma starter in init already has migrations
• use rewritten introspection in migration engine
• [EPIC] Move prisma 2 rust code from prisma repo to somewhere else
• Zeit Now Deployment
• Serverless (Faas) compatibility
• [Suggestion] Optimize the Prisma2 Spec Document Example
• Documentation should clarify not implemented features
• Cannot use @relation(id) to specify the side of the relation
• Prisma2 and Docker
• Prisma2 CLI is binary on Ubuntu 16.04 doesn't link to install libssl
• ID not incremented on MySQL and Postgres
• Fetch the correct binary for EC2 started with Amazon Linux 2 + x86
• Create a Windows Binary

Fixed by the new init flow

• ENOENT running prisma2 init
• Init flow requires an empty directory
• Prisma CLI merges graphql and graphql-auth examples when "GraphQL Boilerplate" is selected in `prisma2 init
• EPIC Implement new prisma init CLI flow
• When connecting to existing MySQL, prisma2 init wizard ends at the introspect step and does not select prisma tools ( Photon, Lift ) nor generate any boilerplate.
• CLI generated undefined when you enter and delete a field in database credentials flow.

photonjs

• Add pretty datamodel parser error for get_config

2.0.0-preview-8

Today, we are issuing the eighth Preview release: 2.0.0-preview-8 (short: preview-8).

Fixes and improvements per Prisma 2 repository

prisma2

• SQLite relative path is broken
• Tab characters make schema parser unhappy + unclear error
• MySQL 5.7 "Error in lift engine for rpc listMigrations" when DB name has a hyphen

2.0.0-preview-7

Today, we are issuing the seventh Preview release: 2.0.0-preview-7 (short: preview-7).

Major changes

With this release, we've put major efforts into making Lift's migration engine more performant. Especially remote migrations benefit from significant performance improvements in this release.

Fixes and improvements per Prisma 2 repository

prisma2

• Prisma on linux
• Drop support for recognizing project.prisma files
• Photon QueryError because WrongType(Type(Text)) for @default(uuid()) on Postgres
• Error when using Photon to create new item with 2 relation connections
• Query engine fails for querying implicit back relation

lift

• Create model with enum array throws: no such table
• Remote migrations are very slow

photonjs

• notIn throws type error with empty array
• __internal is ignored

2.0.0-preview-6.1

Fixes

There was a problem in packaging the cli in the 2.0.0-preview-6 release, which broke most commands.

2.0.0-preview-6

Today, we are issuing the sixth Preview release: 2.0.0-preview-6 (short: preview-6).

Major changes

Next to a lot of bug fixes, this release ships with a completely overhauled core of the Prisma query engine which makes the resolution of Photon queries a lot more stable.

Unfortunately, due to the overhaul there is one known regression to be aware of: Required relations are not enforced as NOT NULL on the database level. They are enforced by the query engine though. This is intermediate until we have fixed a limitation in the query engine. You can track the progress of this issue here.

Fixes and improvements in the Prisma 2 repository

prisma2

• [Preview3]Error when prisma2 generate
• prisma2 generate generates files into wrong directory
• Init flow creates projects inside a "prisma" folder, if it exists

photonjs

• Now dev causes: Cannot find module "node_modules/@generated/photon/index.d.ts"
• photon.dmmf.schema.outputTypes has duplicated Query & Mutation
• Photon is not throwing a full Rust backtrace for panics
• updateMany should return count of updated records
• Inconsistent type generation
• Support empty where statement for findMany
• "set" throwing error
• Correct the description
• sqlite @id @default(cuid()) marks field as required
• ID not incremented on MySQL
• SQLite: Queries in large tables result in error: "too many SQL variables"
• RelationFieldNotFound on nested create/connect
• Self-referential Data Modeling Leads to Unexpected Behavior
• NullConstraintViolation related to DateTime type
• Postgres + @@map causes a crash
• Error for Float type (postgresql)
• Simple nested update mutation fails
• Bring your own ID fails

lift

• Lift engine only supports new versions of MySQL ( >= 5.7 ).
• Lift "duplicate column name:"
• [Preview3.2]MySQL Lift Bug
• Error in lift engine
• The schema snapshot file is still called datamodel.prisma