P3: Next major version Epic

[matthewmueller]

Situation

Prisma is adopting Semver to provide clearer expectations about upgrade compatibility. Our next major release will be Prisma 3. This epic is for gathering issues we'd like to complete prior to releasing Prisma 3.

Issues

Turn Node-API on by Default (Must Have)

We'd like to make Node-API the default interface between the Typescript client and the Query Engine. These issues were pulled from our internal project board.

• Make Node-API library default engine #8731
• Bump Node.js requirement from to >=12.2 to >=12.6 #8839
• Document Node-API library docs#1895
• Preview feature feedback: Node-API support (nApi) #6301

Stabilize referentialActions (Must Have)

• Remove referentialActions preview flag #8633
• Preview feature feedback: Referential Actions (referentialActions) #7816

Stabilize namedConstraints (Must Have)

• https://github.com/prisma/migrations-team/issues/264
• implement named default constraints for SqlServer
• Remove residual NamedConstraint gating prisma-engines#2199
• https://github.com/prisma/migrations-team/issues/247 (stretch goal)
• Preview feature feedback: Define custom Constraint Names (namedConstraints)  #8616

Promote SQL Server to Generally Available (Must Have)

We're planning to promote our SQL Server for the Prisma 3 launch. The following issues were pulled from our internal project board.

• SQL Server: migrate dev (and db push) does not create a database #8058
• QueryResult will lose the column metadata tiberius#165
• MSSQL: Epic - Transform SQL Server preview documentation into permanent documentation docs#1957
• Remove microsoftSqlServer preview flag #4537
• Preview feature feedback: microsoftSqlServer #4039

Deprecate the prisma introspect command in favor of prisma db pull (Must Have)

• Update docs to reflect that prisma introspect gets deprecated in favor of prisma db pull docs#2115
• CLI: Add deprecation notice to prisma introspect (renamed db pull) #8078

Fix $queryRaw SQL Injection (Must Have)

We'd like to take this opportunity to fix a footgun in our API where it's really easy to accidentally make your application susceptible to SQL injections.

• Revisit prisma.$queryRaw("...") vs. prisma.$queryRaw template literal #7142
• Add runtime check to $queryRaw("...") to throw for JS calls #8808
• Write a codemod to rename $queryRaw(...) to $queryRawUnsafe(...) #8809
  • Update Sept 3rd: We won't have time to make this codemod, this will be an easy find and replace anyway.

JSON Null Equality Breaking Changes (Must Have)

• Can't filter by null values on JSONB fields #8399
• JSON field can not query for "not equals" #7836

Release Pipeline Adjustments (Must Have)

• https://github.com/prisma/prisma-private/issues/147

Rework db seed (Must have)

• EPIC: re-design of db seed feature #8732
• Review and merge fix(db seed): redesign of db seed #8146
• Update docs db seed GA docs#2161
• QA db seed
• db seed tests need to run on multiple platforms, not just Ubuntu #8033
• e2e Test seeding ecosystem-tests#1806
• Update Preview feature feedback: Integrated seeding  #5161
• Close issues and let users know that they can use the new version https://github.com/prisma/prisma/issues?q=is%3Aissue+label%3A%22topic%3A+db+seed%22+is%3Aopen

Stabilize orderByRelation (Nice to Have)

We'd like to promote orderByRelation from preview to generally available.

• Order By Relation with CursorId doesn't return result #8036
• Order by Relations with multiple references #7331
• Remove preview flag for orderByRelations #8629
• Preview feature feedback: Order by Relations support (orderByRelation) #5438

Stabilize orderByAggregateGroup (Nice to Have)

We'd like to promote orderByAggregateGroup from preview to generally available.

• Remove preview flag for orderByAggregateGroup #8630
• Preview feature feedback: Order by an Aggregate in groupBy (orderByAggregateGroup) #6545

Stabilize selectRelationCount (Nice to Have)

We'd like to promote selectRelationCount from preview to generally available.

• Prisma client crashes when counting m-n self-relation #7807
• Prisma crashes when I use the same table for counting and findUnique #7893
• Queries that include the count of a relation that has multiple foreign keys translates to incorrect SQL #7299
• Shows incorrect count number by using selectRelationCount previewFeatures #8050
• Remove preview flag for selectRelationCount #8631
• Preview feature feedback: Find a relation's count (selectRelationCount ) #6312

Stabilize filterJson (Nice to Have)

• JSON number filtering bug #8224
• Json filters array_starts_with and array_ends_with don't work on MariaDB #8874
• Postgres "json" column type throws errors with JSON filtering's array_contains #8977
• Remove preview flag for filterJson #8632
• Preview feature feedback: Filtering Json fields (filterJson) #7135
  • Update Sept 3rd: We fixed some bugs, but won't stabilize filterJson for Prisma 3.

Aggregation API

• Remove non-underscored fields (e.g. count should be _count) #9029

Docs

• P3: New major version documentation Epic docs#2116
• update docs to reflect new attribute signatures
• remove preview flags from docs once everything above goes GA
• update examples to use new syntax / names / capabilities

References

• Why Prisma is Adopting Semver
• Internal Prisma 3.0 Planning Document
• Internal Node-API Project Board
• Internal SQL Server Project Board