What types of Referential Integrity constraint can be coded to maintain consistency between the rows of two tables:

Question

BlackTom AI · Accepted Answer

Let's break down the question and each option to understand referential integrity constraints that keep two tables in sync.
Option 1: Waterfall. This term is not a standard referential integrity action in relational databases. It sounds like a metaphor rather than a defined constraint, so it does not describe a valid mechanism to enforce consistency between related rows.
Option 2: Restrict. This is a recognized referential action. When you set a foreign key constraint to RESTRICT, the database prevents the operation that would create a violation, such as deleting a parent row or updating a key that has dependent child rows. This directly maintains consistency between the related tables by disallowing actions that would break the link.
Option 3: Self Referencing. While self-referencing (or self-join/foreign key referencing the same table) is a valid design pattern to model hierarchical data, it is not itself a referential integrity action between two distinct tables. It describes how rows relate within a single table, not how integrity is enforced across two tables.
Option 4: Set-to-Nothing. This phrasing resembles a description of a referential action like SET NULL or SET DEFAULT, which are standard options in many RDBMSes. However, the exact term "Set-to-Nothing" is not a canonical, officially supported action. If interpreted as SET NULL, it does maintain referential integrity but under a specific rule; as written, "Set-to-Nothing" is not a standard label and thus is not the correct canonical answer in typical exam contexts.
In summary, among the given choices, Restrict is the standard, correctly named referential integrity constraint used to maintain consistency between related rows in two tables by preventing deletions or updates that would violate the relationship.

What types of Referential Integrity constraint can be coded to maintain consistency between the rows of two tables:

查看解析

登录即可查看完整答案

类似问题

Which type of key can enforce rules such as cascading updates or deletions?

Question at position 41 A referential integrity constraint specifies that the existence of an attribute in one table depends upon the existence of a foreign key in the same or another table.TrueFalse

Question at position 50 A referential integrity constraint specifies that the existence of an attribute in one table depends upon the existence of a foreign key in the same or another table.TrueFalse

Question at position 32 Requiring a CustomerID to exist in a Primary table before it can exist in a foreign table is an example of:the Hoffer Principle.referential integrity.key constraints.referential referring.

Question at position 36 A referential integrity constraint specifies that the existence of an attribute in one table depends upon the existence of a foreign key in the same or another table.TrueFalse

Question at position 7 Requiring a CustomerID to exist in a Primary table before it can exist in a foreign table is an example of:referential referring.referential integrity.the Hoffer Principle.key constraints.

Question at position 53 A referential integrity constraint specifies that the existence of an attribute in one table depends upon the existence of a foreign key in the same or another table.TrueFalse

Question at position 43 A referential integrity constraint specifies that the existence of an attribute in one table depends upon the existence of a foreign key in the same or another table.TrueFalse

更多留学生实用工具

考试浏览器助手

风格化写作助手

论文查重助手

文献引用助手

课堂转译助手

课堂笔记助手

Quiz搜索助手

学校历年真题

智能刷题助手

智能匹配练习

希望你的学习变得更简单