数据库系统概论之范式讲解_域键范式| 数据库管理系统

数据库系统概论之范式讲解

A domain-key normal form is a normal form used in database normalization which needs particularly that the database contains no restrictions other than domain constraints and key constraints.

域键范式是数据库规范化中使用的范式，尤其需要数据库除域约束和键约束之外不包含其他任何约束。

A domain constraint identifies clearly the permitted and enabled values for a given attribute, while a key constraint identifies clearly the attributes that distinctly identify a row in a given table or relation.

域约束清楚地标识了给定属性的允许值和启用值，而键约束清楚地标识了明确标识给定表或关系中行的属性。

It is fundamentally a process in the database to arrange systematically data efficiently and effectively. Fundamentally, there are two targets of doing normalization, which are as follows,

从根本上说，这是数据库中高效有效地整理数据的过程。 从根本上讲，进行标准化的目标有两个，如下所示：

1. To eliminate repeated data or in other words, it can be said to eliminate redundant data.

   为了消除重复数据或换句话说，可以说消除了冗余数据。

2. It is to make certain that there will be data dependencies.

   确保存在数据依赖性。

The domain/key normal form is successfully reached when each constraint on the relation or table of the attribute is a logical consequence of the definition of keys and domains, and imposing key and domain restraints and conditions, which causes all constraints to be arranged. That's why it avoids all non-temporal anomalies. To achieve Normalization, the steps to be taken are,

当对属性的关系或表的每个约束是键和域的定义的逻辑结果，并强加键和域的约束和条件时，就可以成功达到域/键范式。 因此，它避免了所有非时间异常。 为了实现标准化，需要采取的步骤是：

1. Eliminate repeating groups and remove repeating data.

   消除重复的组并删除重复的数据。

2. Eliminate those columns that are not considered to be dependent on Key.

   消除那些不依赖于Key的列。

3. The multiple relationships should be separate independently.

   多个关系应该独立地分开。

It's very effortless to construct a database in the domain/key normal form than it is to change the form of lesser databases which may have in a great number of anomalies. Although, successfully constructing a domain/key normal form database continue to exist as a challenging task, even for experienced database programmers. Thus, in the duration of time the domain/key normal form removes the problems found in most databases, it inclined to be the most costly normal form to achieve. However, unsuccessful to achieve the domain/key normal form may carry long-term, hidden costs due to anomalies which become noticeable in databases attached only to lower normal forms over a period of time.

以域/密钥标准格式构造数据库比更改可能存在大量异常的较小数据库的形式要容易得多。 尽管成功地构建域/密钥范式数据库仍然是一项艰巨的任务，即使对于有经验的数据库程序员而言也是如此。 因此，在一段时间内，域/密钥范式消除了大多数数据库中发现的问题，它倾向于实现成本最高的范式。 但是，由于无法正常获得域/密钥常规格式，因此可能会带来长期的长期隐藏成本，因为异常会在一段时间内仅附加到较低常规格式的数据库中变得明显。

The fundamental scheme behind the domain/key normal form is to identify the normal form that takes into account all the possible dependencies and constraints.

域/密钥范式背后的基本方案是确定考虑所有可能的依赖关系和约束的范式。

In easily understood manner, the domain/key normal form define as a normal form utilized in database normalization which needs particularly that the database which have no constraints other than domain constraints and key constraints.

以容易理解的方式，域/密钥范式定义为在数据库归一化中使用的范式，该范式特别需要除域约束和密钥约束之外没有约束的数据库。

In other words, the domain/key normal form contain a relation schema only if all constraints and dependencies that should hold on the valid relation state can be imposed by easily imposing the domain constraint and key constraint on the relation or table of attributes. For a relation in the domain/key normal form, it becomes very straight forward to impose all the database constraints by simply examining so that each attribute value is a tuple is of the suitable domain and that every key constraint is imposed.

换句话说，仅当可以通过轻松地将域约束和键约束强加在关系或属性表上来强加应保留在有效关系状态上的所有约束和依赖关系时，域/键范式才包含关系模式。 对于域/密钥标准形式的关系，通过简单地检查以使每个属性值都是一个适合域的元组并强加每个密钥约束，来强加所有数据库约束变得非常简单。

The reasons to utilize the domain/key normal form are in the following points,

使用域/密钥范式的原因有以下几点：

1. To avoid general constraints in the database those are not clear key constraints.

   为了避免数据库中的一般约束，这些不是明确的关键约束。

2. Most databases can easily test or check key constraints on attributes.

   大多数数据库可以轻松测试或检查属性的关键约束。

A table is in Domain-Key normal form only if it is in 4NF, 3NF and other normal forms. It is based on constraints:

仅当表采用4NF，3NF和其他常规格式时，它才具有Domain-Key常规格式。 它基于约束：

域约束 (Domain constraint)

Values of an attribute had some set of values, for example, EngineerID should be four digits long:

属性的值具有一些值集，例如， EngineerID应该为四位数长：

EngineerID	Engineer Name	Engineer Age
0443	Rakesh	34
0546	Kamal	27

工程师编号	工程师姓名	工程师年龄
0443	拉克什	34
0546	卡马尔	27

关键约束 (Key constraint)

An attribute or its combination is a candidate key.

属性或其组合是候选键。

一般约束 (General constraint)

Predicate on the set of all relations.

确定所有关系的集合。

Although, because of the difficulty of including complicated constraints in the domain/key normal form relation its practical utility is limited means that they are not in practical use, as long as it may be quite difficult to identify general integrity constraints.

尽管由于难以在域/密钥范式关系中包含复杂的约束，但是其实用性受到限制，这意味着它们无法实际使用，只要可能很难确定一般的完整性约束即可。

翻译自: https://www.includehelp.com/dbms/domain-key-normal-form.aspx

数据库系统概论之范式讲解