[Prisma Migrate with SQL Server errors with Error: Invalid data source URL, see https://www.prisma.io/docs/reference/database-reference/connection-urls in 2.22.0 #6984](prisma/prisma#6984)
2.22.0
Today, we are excited to share the 2.22.0 stable release 🎉
🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟
Major improvements & new features
prisma db push is now Generally Available
prisma db push enables you to update the database schema from the Prisma schema file, without generating any migrations.
This is especially useful when prototyping a new feature, iterating on the schema changes before creating migrations or generally if you are at stage of your development process, where you don't need to persist the schema change history via database migrations.
You can find more info on prisma db push in the official docs.
Deprecation of array notation for provider fields
In this release, we are also entirely removing the array notation for the provider fields on datasource blocks. This has been deprecated since 2.11.0 (November 2020).
You can read more about our reasons for this deprecation here.
Prisma Client Go gets support for AND operator
We've always had OR, but this release we also added AND support:
This version was pushed to npm by prismabot, a new releaser for @prisma/client since your current version.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Bumps @prisma/client from 2.11.0 to 2.22.1.
Release notes
Sourced from
@prisma/client
's releases.... (truncated)
Commits
701f1c2
test: fix mysqlUnknown database 'tests'
566541c
test: fix mssql snapshots90c4c50
test: fix buildkite env vars0434cff
test: fix buildkite env vars4d06c0d
test: fix buildkite env varsff302da
test: fix sql server86d0be3
test: fix sql serverb91f832
test: fix postgres2949f9b
test: revert to localhost + fix drop sqlserver73e53eb
tests(migrate,cli): add mysql + sql server public tests for db pull & migrate...Maintainer changes
This version was pushed to npm by prismabot, a new releaser for
@prisma/client
since your current version.Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)