The Event Organizer's Toolbox aims to provide a platform where event organizers can manage important information pertaining to their events without having to use multiple additional tools to stay organized.
🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟
Highlights
In this sprint, we’ve made bug fixes and overall improvements to Prisma Client. We’ve been working on a few projects that will be announced soon. Stay tuned for the upcoming releases for updates!
Improvements and bug fixes
We made the following changes:
Prisma Client improvements
Validation for undefined values in arrays in Json fields
We added runtime validation for undefined values in arrays in Json fields. Prisma Client will now return an error when an array contains an undefined value. Therefore, we encourage you to add validation that either removes the value or transforms it to null if you stumble on the runtime validation:
// Example error message on running the query
Can not use undefined value within array. Use null or filter out undefined values
Performance improvements for models with many unique fields
This release improves Prisma Client’s memory consumption for models with many @unique constraints. This was a regression from version 4.10.1, where in some cases, if a model had many unique constraints, Prisma Client would use up a lot of available memory.
Fixed the segmentation fault error that used to occur on ARM64 Linux binary targets
Metrics Preview feature improvements:
We updated the counters and gauge properties
We fixed the bug that caused the prisma_pool_connections_open metric to have a negative value in some cases.
Prisma Migrate improvements
Fixed an introspection bug for MongoDB views. Previously, if a MongoDB database contained a view, prisma db pull would throw an error. We resolved this, and views are now ignored.
Added the PRISMA_SCHEMA_DISABLE_ADVISORY_LOCK environment variable that enables you to disable advisory locking.
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 show ignore conditions` will show all of the ignore conditions of the specified dependency
- `@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 from 4.15.0 to 5.3.0.
Release notes
Sourced from prisma's releases.
... (truncated)
Commits
49ec0ac
feat(cli): add version, and help, to commands and flags output (#20900)99f5626
fix(deps): update dependency node-fetch to v2.7.0 (#20892)05331eb
chore(deps): update jest to v29.6.4 (#20891)fd5e07d
chore: use dotenv-cli for db urls (#20847)2ca3944
ci: type check codebase (#20855)6c58bf4
fix(generate): Empty line before usage instructions (#20859)f80180a
fix(deps): update dependency node-fetch to v2.6.13 (#20812)c648da2
chore: update typescript@5.2.2 (#20850)71fed12
chore(deps): update jest (#20810)a7e4353
test(cli): studio via mini-proxy (#20781)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 show