v8.0.0-rc.11-dev.42: docs: close out the createAll conflict-skip project (#30371)

发生了什么

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.…

摘要按规则整理自下方来源原文

来源