drizzle-orm-fk-references-must-be-explicit
Drizzle ORM schema columns declared as plain int (e.g., teamId, assigneeId, creatorId) do NOT auto-generate foreign key constraints — .references() must be called explicitly on each column. Without this, deletions silently create orphaned rows with no DB-level integrity enforcement. This is a common Drizzle gotcha when developers assume ORM column naming implies referential integrity.
Related
- drizzle-orm-fk-omission-causes-orphaned-rows
- drizzle-orm-foreign-keys-not-implicit-must-use-references
- drizzle-orm-does-not-auto-enforce-foreign-keys
- drizzle-fk-references-omitted-by-default-causes-orphans
- drizzle-orm-foreign-keys-not-auto-enforced
- drizzle-orm-foreign-key-omission-causes-orphaned-rows
- drizzle-orm-foreign-keys-not-enforced-by-default
- drizzle-orm-foreign-keys-not-added-automatically