Question

我有一个客户、中间项目类型数据库。

Customers can buy many items and this is stored in the "middle" table, with just the two columns with customerid and itemid.

我目前正在使用我的仪表进行所有表格。

Is it recommended to use Innodb for the middle table in this structure?

Answer 1

我倾向于InnoDB,因为:

InnoDB should be used where data integrity comes a priority because it inherently takes care of them by the help of relationship constraints and transactions. Faster in write-intensive (inserts, updates) tables because it utilizes row-level locking and only hold up changes to the same row that’s being inserted or updated.

而

MyISAM is simpler to design and create, thus better for beginners. No worries about the foreign relationships between tables. Faster than InnoDB on the whole as a result of the simpler structure thus much less costs of server resources. Full-text indexing. Especially good for read-intensive (select) tables.

比较非常简单。非行更适合需要经常插入和更新的数据危急情况。而另一方面,我的国际宇宙航行科学院的运行情况较好,其应用并不完全取决于数据的完整性,而且大多只是选择和显示数据。

希望这一帮助。

Answer 2

INNODB Support foreign key restrictions 包括可在禁止令表上删除的单体字。

排放物删除(仅限量)使 your子能够自行清理。

If your junction table employs foreign key constraints with cascading deletes and you remove either a customer or item record, the matching middle record will be removed so it does not become orphaned.

页: 1

Answer 3

因诺德允许你确定冷却 for子。

你们的伤口具有一些特点:

foregin-keys can delete / update depending datas too.
foregin-keys can reject deletings/updates if dependings exists.

通常情况下,使用原基钥匙的提早决定:那些原基钥匙需要额外的编码限制,即你可能无法在没有客户或物品的情况下插入中间物。

友情链接