v8.0.0-rc.11-dev.42: docs: close out the createAll conflict-skip project (#30371)
- Prisma: 108 events in the last 90 days
- Prisma: 108th Release in the last 90 days
- Previous: earlier the same day · v8.0.0-rc.11-dev.41
What happened
Decision Delete projects/createall-conflict-skip/ now that the feature it shaped has merged ( #30365 ), and keep the one design rule from it that outlives the project. What moves The design notes recorded why conflictOn is optional on createAll(rows, { onConflict: 'skip' }) even though the option works without it: Postgres and SQLite can skip on any unique constraint, but SQL Server cannot skip without a named key.…
Summary assembled by rule from the sources below