First normal form
Minimum requirement in database normalization
First normal form (1NF) is the most basic level of database normalization defined by English computer scientist Edgar F. Codd, the inventor of the relational database. A relation (or a table, in SQL) can be said to be in first normal form if each field is atomic, containing a single value rather than a set of values or a nested table.
Nº Q1366465 ★★
Peu commune · Histoire
First normal form
Minimum requirement in database normalization
First normal form (1NF) is the most basic level of database normalization defined by English computer scientist Edgar F. Codd, the inventor of the relational database. A relation (or a table, in SQL) can be said to be in first normal form if each field is atomic, containing a single value rather than a set of values or a nested table.
Sur Wikipédia
Texte en anglais Pas encore d'article dans ta langue : extrait en anglais.
First normal form (1NF) is the most basic level of database normalization defined by English computer scientist Edgar F. Codd, the inventor of the relational database. A relation (or a table, in SQL) can be said to be in first normal form if each field is atomic, containing a single value rather than a set of values or a nested table. In other words, a relation complies with first normal form if no attribute domain (the set of values allowed in a given column) has relations as elements. Most relational database management systems do not support creating or using table-valued columns, which means most relational databases will be in first normal form by necessity. Otherwise, normalization to 1NF involves eliminating nested relations by breaking them up into separate relations associated with each other using foreign keys. This process is a necessary step when moving data from a non-relational (or NoSQL) database, such as one using a hierarchical or document-oriented model, to a relational database. A database must satisfy 1NF to satisfy further "normal forms", such as 2NF and 3NF, which enable the reduction of redundancy and anomalies. Other benefits of adopting 1NF include the introduction of increased data independence and flexibility (including features like many-to-many relationships) and simplification of the relational algebra and query language necessary to describe operations on the database. Codd considered 1NF mandatory for relational databases, while the other normal forms were merely guidelines for database design.
Texte : Wikipédia en anglais, CC BY-SA 4.0. ·
Cartes voisines
-
S
Second normal form
Database normalization requirement after first normal form
Nº Q277396 ★★
Pas en vente
-
T
Third normal form
Normalizing a database design to reduce the duplication of data and ensure referential integrity
Nº Q311585 ★★
Pas en vente
-
Relation (database)
Concept in relational database theory
Nº Q277521 ★★
Pas en vente
-
S
Sixth normal form
Relational database normalization form which generalizes relational operators to support interval data
Nº Q4523348 ★
Pas en vente
-
F
Fourth normal form
Normal form used in database normalization concerned with multivalued dependency
Nº Q2492261 ★
Pas en vente
-
E
Edgar Frank Codd
Informaticien britannique
Nº Q92596 ★★
Pas en vente