Skip to content
This repository was archived by the owner on Feb 13, 2023. It is now read-only.

build(deps): bump @prisma/sdk from 3.7.0 to 3.11.1 in /packages/generator#40

Closed
dependabot[bot] wants to merge 1 commit intomasterfrom
dependabot/npm_and_yarn/packages/generator/prisma/sdk-3.11.1
Closed

build(deps): bump @prisma/sdk from 3.7.0 to 3.11.1 in /packages/generator#40
dependabot[bot] wants to merge 1 commit intomasterfrom
dependabot/npm_and_yarn/packages/generator/prisma/sdk-3.11.1

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Mar 24, 2022

Bumps @prisma/sdk from 3.7.0 to 3.11.1.

Release notes

Sourced from @​prisma/sdk's releases.

3.11.1

Today, we are issuing the 3.11.1 patch release.

MongoDB (Preview)

Breaking: Filters no longer return undefined fields by default

In 3.11.1, we've changed what data is returned when filtering MongoDB documents on undefined fields. The new rule is that undefined fields are excluded by default unless explicitly filtered for. This allows you to query for undefined and null values separately.

Let's take a look at a concrete example. Given the following Prisma schema:

model Address {
    id     Int    @id @map("_id")
    city   String
    street String? // Note that street is optional
}

For Mongo, optional fields can either be null or undefined (absent). The following documents are all valid for the schema above:

{ "_id": 1, "city": "San Fransisco", "street": "Market st." }
{ "_id": 2, "city": "Seattle", "street": null }
{ "_id": 3, "city": "Chicago" }

Prior to 3.11.1, if you queried for where: { street: null }, you'd get _id: 2 and _id: 3. In 3.11.1, you'll only get _id: 2. The ability to also query for the missing fields has also been added. For details, refer to the new isSet below to learn more.

There are a few exceptions to this new default:

  • A having filter on an aggregated field will return undefined fields. This is because aggregation on undefined fields yields null, not undefined, thus matching the filter.
  • Filters on undefined to-many relations (e.g., the backing array of a many-to-many is undefined) will currently include those relations in the result set.

New isSet filter operation

To compensate for missing fields on documents no longer being returned by the filters above, we’ve added a new isSet: bool filter. This filter can be used to include fields that are undefined on documents.

Using the example above, to include the undefined fields, you can use an OR:

await prisma.address.findMany({
  where: {
    OR: [
      { street: { isSet: false } },
      { street: null }
    ]
  }
})

... (truncated)

Commits
  • d578fc6 test(sdk): update snap
  • 367aaed chore: bump engines
  • 6555c2e test(sdk): update snaps
  • 9f6f07f feat(client): composite filtering (#12271)
  • 6561b8a chore(deps): update engines to 3.11.0-46.c9f86866d2fb27b2066e5447ee7f6f65c46c...
  • 695537a test(client): increase timeout for 1 Windows/macOS test (#12317)
  • 88b6265 chore(deps): update engines to 3.11.0-44.de508c1bd4bac0d723b519cc484e96e8c42f...
  • a71a46c chore(deps): update engines to 3.11.0-43.46710cce5c925c7223e8684ea24f44fbeae3...
  • 2bf91d8 chore(deps): update engines to 3.11.0-42.e996df5d66a2314d1da15d31047f9777fc2f...
  • 13d68d7 chore(deps): update engines to 3.11.0-40.e996df5d66a2314d1da15d31047f9777fc2f...
  • Additional commits viewable in compare view

Dependabot compatibility score

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/sdk](https://github.com/prisma/prisma/tree/HEAD/packages/sdk) from 3.7.0 to 3.11.1.
- [Release notes](https://github.com/prisma/prisma/releases)
- [Commits](https://github.com/prisma/prisma/commits/3.11.1/packages/sdk)

---
updated-dependencies:
- dependency-name: "@prisma/sdk"
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Mar 24, 2022
@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Apr 5, 2022

Superseded by #42.

@dependabot dependabot bot closed this Apr 5, 2022
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/packages/generator/prisma/sdk-3.11.1 branch April 5, 2022 20:40
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants