MySQL 设置cascade on delete on update

最新推荐文章于 2025-06-29 21:05:28 发布

转载最新推荐文章于 2025-06-29 21:05:28 发布 · 4.9k 阅读

文章标签：

#delete #mysql #components #include #null #types

MySQL 专栏收录该内容

4 篇文章

订阅专栏

本文详细介绍了一个用于存储组件信息的数据库表的设计方案。该表包括id、typeId和moreInfo等字段，并通过外键约束与类型表关联，确保数据的一致性和完整性。特别强调使用InnoDB存储引擎以支持外键。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >


Here's what you'd include in your components table.

CREATE TABLE `components` (
    `id` int(10) unsigned NOT NULL auto_increment,
    `typeId` int(10) unsigned NOT NULL,
    `moreInfo` VARCHAR(32), 
    -- etc
    PRIMARY KEY (`id`),
    KEY `type` (`typeId`)
    CONSTRAINT `myForeignKey` FOREIGN KEY (`typeId`)
      REFERENCES `types` (`id`) ON DELETE CASCADE ON UPDATE CASCADE
)
Just remember that you need to use the InnoDB storage engine: the default MyISAM storage engine doesn't support foreign keys.