TML-3762: MongoDB migrations create and drop each index by its name, so two indexes on the same fields can exist together by wmadden-electric · Pull Request #30952 · prisma/orm

MongoDB contracts record each index's name, and migrations create, drop and verify indexes by name

wmadden-electric

committed

ee41623

Example contracts, migrations and integration tests name every MongoDB index, and a real database holds indexes on the same keys under their own names

wmadden-electric

committed

1b86641

ADR 317 records that MongoDB indexes carry their names, and the upgrade note names the indexes of old contract snapshots

wmadden-electric

committed

34399fc

Dropping a text index read back from MongoDB checks the weights MongoDB lists, so db update can drop it

wmadden-electric

committed

a7b62e5

The language server offers map on MongoDB index attributes

wmadden-electric

committed

90ac5b3

db update and db init compare a database's indexes as db verify does, so text indexes and partly written collations plan nothing

wmadden-electric

committed

6339401

defineContract names index refusals by the positions the model wrote, also after a merged index

wmadden-electric

committed

b503a2e

The upgrade script names snapshot indexes as the emitted contract does, and the docs say dropIndex lists every option and rewritten snapshots keep their hash

wmadden-electric

committed

64205ba

db init and db update create each index as the contract writes it, every schema states whether it was read from a database, and a database created from retail-store plans nothing

wmadden-electric

committed

9698eb7

MongoDB PSL index diagnostics quote both indexes as the schema writes them

wmadden-electric

committed

8cb3cb3

The upgrade script names snapshot indexes from their own project's emitted contract, reports every index it names after its keys, and writes files as contract emit does

wmadden-electric

committed

8bc7eb9

The upgrade script never takes an index name from beyond the snapshot's project root, the first folder with a package.json

wmadden-electric

committed

eb3aa43

Merge remote-tracking branch 'origin/main' into tml-3762-mongo-index-names

wmadden-electric

committed

8fbb96b

Navigation Menu

Repository navigation

TML-3762: MongoDB migrations create and drop each index by its name, so two indexes on the same fields can exist together - #30952

TML-3762: MongoDB migrations create and drop each index by its name, so two indexes on the same fields can exist together#30952
wmadden merged 21 commits into
mainfrom
tml-3762-mongo-index-names

Commits on Nov 5, 2026

MongoDB contracts record each index's name, and migrations create, drop and verify indexes by name

Example contracts, migrations and integration tests name every MongoDB index, and a real database holds indexes on the same keys under their own names

ADR 317 records that MongoDB indexes carry their names, and the upgrade note names the indexes of old contract snapshots

Dropping a text index read back from MongoDB checks the weights MongoDB lists, so db update can drop it

The language server offers map on MongoDB index attributes

db update and db init compare a database's indexes as db verify does, so text indexes and partly written collations plan nothing

defineContract names index refusals by the positions the model wrote, also after a merged index

The upgrade script names snapshot indexes as the emitted contract does, and the docs say dropIndex lists every option and rewritten snapshots keep their hash

db init and db update create each index as the contract writes it, every schema states whether it was read from a database, and a database created from retail-store plans nothing

MongoDB PSL index diagnostics quote both indexes as the schema writes them

The upgrade script names snapshot indexes from their own project's emitted contract, reports every index it names after its keys, and writes files as contract emit does

The upgrade script never takes an index name from beyond the snapshot's project root, the first folder with a package.json

Merge remote-tracking branch 'origin/main' into tml-3762-mongo-index-names

Commits on Nov 6, 2026

The monorepo upgrade-script test compares the whole folder after the run, so the untouched project's contract is checked too

ADR 317 opens with a Prisma 8 example, builds up why MongoDB indexes need names, and describes the system as it is, without ticket links or upgrade steps

ADR 317 says why MongoDB index names hold no content hash: MongoDB index content compares exactly

The upgrade script skips symlinks, and ADR 317 says redundant indexes merge before the duplicate-name refusal

The upgrade script names each symbolic link it does not follow and exits 1, so snapshots behind a linked migrations folder are not skipped silently

Merge remote-tracking branch 'origin/main' into tml-3762-mongo-index-names

The MongoDB PSL init starter's pinned storage hash includes its index name

Merge remote-tracking branch 'origin/main' into tml-3762-mongo-index-names