[pull] main from prisma:main #81
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![pull[bot]](https://avatars.githubusercontent.com/in/12910?s=60&v=4){kind=small}
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
#24509) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…945 (#24501) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…24481) * feat(client): added provider compatibility check for Driver Adapters * chore(client): removed mock adapterName stub * chore(client): adapted mock adapterName stub * chore(client): remove console.logs * test(client): fix failures in Node.js 16? * test(client): get rid of libsql, which is not compatible with Node.js 16 * test(client): revert "breaking" change, due to panics happening in Rust. Added comments with TODo * chore: fix tests? * chore: fix tests?? * chore: fix tests, add D1 * chore: fix type tests * chore: fix type tests? * chore: fix type tests + module resolution issues with mock-adapter * chore: fix e2e tests??? * chore: fix e2e tests?????? * test(client): split e2e "prisma-client-imports" in different test suite for each Driver Adapter provider * chore: update pnpm-lock * chore: removed unused undici import
…14.0 (#24542) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…9fc221e9de94 (#24560) * test(client): SQLite "Timed out during query execution." for concurrent queries Reproductions for #11789 * test(client); add more tests * chore(deps): update engines to 5.16.0-1.fix-sqlite-concurrent-writes-74a48e9f33b0a8b403045af35430ce444541be88 * test(client): update tests for D1 * test(client): fix D1 test * test(client): prove that #22947 is solved as well * add DROP before create * chore(client): rename test suite * chore(client): fix mongodb issue? * use `db.dropDb()` * test(client): clean up functional tests, remove non-deterministic IDs * test(client): run only on SQLite * chore(deps): update engines to 5.16.0-16.4c3db41c3ad6086fa0f844bafe039fc221e9de94 * chore(client): fix UTF8 issues with Postgres --------- Co-authored-by: Joël Galeran <[email protected]> Co-authored-by: jkomyno <[email protected]> Co-authored-by: Alberto Schiabel <[email protected]>
Should fix the failures for e2e tests.
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
* feat: display the socket path during migration * affects: PostgreSQL, CockroachDB, and MySQL
* feat(client): Implement global `omit` configuration
Allows to set `omit` option in `PrismaClient` constructor:
```ts
const prisma = new PrismaClient({
omit: {
user: {
password: true
}
}
})
```
If developer does so, specified field will be omitted from all model
results by default as if local `omit` option was specified for every
query. It is still possible to include field explicitly either by using
`omit: { field: false }` or `select: { field: true }` on a query.
Also, just like in case of local omit, if result extension needs omitted
field, we will still query it from DB, but drop before returning the
final result.
Feature implemented under the same `omitApi` preview flag as local `omit`.
Implementation-wise, done by forwarding `ClientOptions` generic all the
way from `PrismaClient` to individual query results. Both local and
global `omit` are now applied at the moment of `DefaultSelection`
creation. Previously, local omit was applied after `select` and `include`,
but that does not work if we want to be able to undo global omit in
individual queries.
Close prisma/team-orm#1109
Ref #5042
* fix extensions tests
* Fix composites selection tests
* Address review feedback
* Render `omit` as required for empty selection
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Alexander Polanco <[email protected]>
The upstream project has been revived since we forked it and has had some improvements, including an official Docker image. Our fork stopped compiling with the latest Go version leading to CI failures, so it's a good opportunity to try switching to the upstream.
…d2e0bd6eea08 (#25027) Co-authored-by: Alexey Orlenko <[email protected]>
Optimize client extension is now using API keys issued in the UI and passed as a parameter to `withOptimize`.
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
* Add types and PrismaClient generation pieces * First semi-working version * Add tests and fix things * Adapt to a new engine * Introduce preview feature * Update snapshots * Restore "loaded" module * Fix serializeRawParameters * Fix package types * Fix invalid JS identifiers * Enums * Pack "sql" files * Fix extension * Fix type error * Try to fix node16 * Better identiifer name check + snapshots * Use export that acutally exists * Add e2e test for default import * Watch support * Fix edge * Fix build * handle column nullability * add nullability tests & sqlite tests * fix nullable sqlite tests * fix bytes test * Fix node types test * Fix lint * Fix DA tests * Ensure esm import works correctly * Fix WASM runtime * Skip planetscale test * Fix sqlite * Fix linter * Throw on unsupported provider * Improve invalid SQL handling * Reuse raw results * Address review * Update snapshots * Fix ecosystem-tests * Remove force flag --------- Co-authored-by: Flavian Desverne <[email protected]>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Closes #24648 The fix changes GetPayloadResult utility type from a mapped type to a combination of an intersection and a mapped type. This way documentation doesn't get erased in the presence of an extension. Tested cases: 1. no extension 2. extension without result extension 3. extension with result extension 4. result extension overwriting a field on base type 5. result extension with the omit feature
* Add the sqlite db to .gitignore * Update the OTEL dependencies to be compatible with Prisma * Update other `devDependencies` in `sandbox/tracing` * Remove unused imports in `sandbox/tracing/index.ts` * Fix deprecated imports * Make it possible to merge PRs that only contain changes in aux files * Ignore the actionlint error * Try to avoid incorrect cli arg parsing * Try to avoid incorrect args parsing v2 * See if we can bring back mapping
… avoid bundling it (#25175)
….0 (#25156) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
* feat(driver-adapter-utils): add TransactionContext definitions and bindings * feat(adapter-planetscale): add support for TransactionContext * feat(adapter-pg): add support for TransactionContext * feat(adapter-pg-worker): add support for TransactionContext * feat(adapter-neon): add support for TransactionContext * feat(adapter-libsql): add support for TransactionContext * feat(adapter-d1): add support for TransactionContext * chore(adapter-*): disable "@typescript-eslint/require-await" * chore(adapter-*): avoid creating a new string when debug logs aren't enabled * chore(deps): update engines to 5.20.0-7.190a98ffde8db4fe0b9ddeea2be06344bbc8edce * test(client): fix mock-adapter in functional tests * test(client): fix mock-adapter in e2e tests --------- Co-authored-by: Alexey Orlenko <[email protected]> Co-authored-by: Prismo <[email protected]>
* chore(e2e): Update next.js to 14 in "schema-not-found" suite Updates next.js and adjusts few things for tests to work afterwards: - `app` directory is no longer experimental and does not need config option. - `standalone` server location can now be different depending on repository structure. - code inside of server components was not idempotent. Calling `create` from a server component have always been wrong, but so far we've been lucky and that caused no issues. That changed after update. Replaced `delete`/`create` calls with `SELECT 1` query instead to avoid consistency issues in case component rendering gets aborted at restarted. Additionally, this adjusts e2e setup to be able to talk to the databases running on a host machine on macOS as well - previously, this worked only on Linux. Close prisma/team-orm#1280 * fix prettier
* added optimize to readme and updated pulse and accelerate links * added studio and changed * removed dataplatform from url
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot]
Can you help keep this open source service alive? 💖 Please sponsor : )