prisma/prisma-engines - CodSpeed

prisma-engines

Blog Docs Changelog

Performance History

Latest Results

chore(deps): bump openssl from 0.10.74 to 0.10.78 Bumps [openssl](https://github.com/rust-openssl/rust-openssl) from 0.10.74 to 0.10.78. - [Release notes](https://github.com/rust-openssl/rust-openssl/releases) - [Commits](https://github.com/rust-openssl/rust-openssl/compare/openssl-v0.10.74...openssl-v0.10.78) --- updated-dependencies: - dependency-name: openssl dependency-version: 0.10.78 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>

dependabot/cargo/openssl-0.10.78

8 days ago

fix: fix JSON insensitive equals (#5806) [TML-2241](https://linear.app/prisma-company/issue/TML-2241/fix-a-query-compiler-like-filter-panic) Fixes https://github.com/prisma/prisma/issues/29440

main

8 days ago

fix: fix JSON insensitive equals

fix/fix-json-insensitive-equals

15 days ago

test/make-create-index-concurrent-portable

16 days ago

fix: support concurrent indexes in shadow db replay (#5799) Support for multiple `CREATE INDEX CONCURRENTLY` statements in migrations was added in https://github.com/prisma/prisma-engines/pull/5767. Shadow DB migration replay still used a separate raw SQL execution path, causing shadow creation to fail if a migration existed with multiple `CREATE INDEX CONCURRENTLY`: ``` Error: P3006 Migration `20260316120000_<migration_name>` failed to apply cleanly to the shadow database. Error: ERROR: CREATE INDEX CONCURRENTLY cannot run inside a transaction block 0: schema_core::state::DevDiagnostic at schema-engine/core/src/state.rs:314 ``` This PR updates the shadow database migration path to use the new migration script logic. This fixes the issue in https://github.com/prisma/prisma/issues/14456#issuecomment-4085815316.  ## Summary by CodeRabbit ## Release Notes * **Bug Fixes** * Improved PostgreSQL database migration execution with enhanced handling for concurrent index operations * Increased reliability in migration application  Co-authored-by: jacek-prisma <malec@prisma.io>

main

16 days ago

Fix Postgres default parsing for `pg_catalog.nextval(...)` (#5802) This fixes a small parsing gap in Postgres introspection. The parser already handled `nextval()`, but not schema-qualified calls like `pg_catalog.nextval()`. In some setups, the database can return the qualified form (not specified), so sequence defaults could be missed. This PR updates the parser to recognize both forms and adds a test. --------- Co-authored-by: jacek-prisma <malec@prisma.io>

main

16 days ago

Merge branch 'main' into fix/shadow-db-multiple-concurrent-indexes

zacharyliu:fix/shadow-db-multiple-concurrent-indexes

17 days ago

chore: fix formatting

Lukasdoe:fix/postgres-pg-catalog-nextval

17 days ago

Latest Branches

0%

chore(deps): bump openssl from 0.10.74 to 0.10.78#5808

8 days ago

2142730

dependabot/cargo/openssl-0.10.78

0%

fix: fix JSON insensitive equals#5806

15 days ago

c2c606d

fix/fix-json-insensitive-equals

0%

test: make the multiple_create_index_concurrently test portable to cockroachdb#5805

16 days ago

3c3fb2d

test/make-create-index-concurrent-portable

© 2026 CodSpeed Technology

Home Terms Privacy Docs