Skip to content

Commit 3f4d75c

Browse files
committed
no-mistakes(document): docs: link conventions note to FK-index option
1 parent f404e1c commit 3f4d75c

1 file changed

Lines changed: 3 additions & 2 deletions

File tree

‎docs/features/metadata-sources.md‎

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -355,8 +355,9 @@ out-of-scope table that already exists would become a proposed `DROP TABLE`.
355355
### `migrate.conventions` — names for objects no code addresses
356356

357357
Beside `scope`, the `migrate` block takes `conventions`: the name of a schema-conventions preset
358-
that decides primary-key and foreign-key constraint names, whether a foreign key gets an index,
359-
and whether a unique key is an index or a constraint. `default` (absent) is what migrate has
358+
that decides primary-key and foreign-key constraint names, whether a foreign key gets an index
359+
(without a preset, [`migrate.foreignKeyIndexes`](migrations-and-drift.md#foreign-key-indexes-migrateforeignkeyindexes)
360+
indexes foreign keys), and whether a unique key is an index or a constraint. `default` (absent) is what migrate has
360361
always emitted; `efcore` is a reference preset that reproduces EF Core's naming. A project can
361362
supply its own conventions from `metaobjects.config.ts` instead. Table, view and column names are
362363
not conventions: they come from `naming`. See

0 commit comments

Comments
 (0)