EF Codd Rule
EF Codd Rule
• Relational Database Management System (RDBMS) because it is based on the relational model
introduced by E.F. Codd.
• Dr. Edgar F. Codd (E.F. Codd) in 1985 after vast research knowledge on the Relational Model of
database presents 13 rules
• These rules test the concept of DBMS against his relational model, and if a database follows the rule,
it is called a true relational database (RDBMS).
Codd Rules in DBMS
• The database must be in relational form. So that the system can handle the database through its
relational capabilities.
• A database contains various information, and this information must be stored in each cell of a table
in the form of rows and columns.
• Every single or precise data (atomic value) may be accessed logically from a relational database
using the combination of primary key value, table name, and column name.
• This rule defines the systematic treatment of Null values in database records. The null value has
various meanings in the database, like missing the data, no value in a cell, inappropriate information,
unknown data and the primary key should not be null.
Codd Rules in DBMS
• It represents the entire logical structure of the descriptive database that must be stored online and is
known as a database dictionary.
• It authorizes users to access the database and implement a similar query language to access the
database.
• The relational database supports various languages, and if we want to access the database, the
language must be the explicit, linear or well-defined syntax, character strings and supports the
comprehensive: data definition, view definition, data manipulation, integrity constraints, and limit
transaction management operations.
• If the database allows access to the data without any language, it is considered a violation of the
database.
Codd Rules in DBMS
• All views table can be theoretically updated and must be practically updated by the database
systems.
• Rule 7 : Relational Level Operation (High-Level Insert, Update and delete) Rule :
• A database system should follow high-level relational operations such as insert, update, and delete in
each level or a single row.
• It also supports union, intersection and minus operation in the database system.
Codd Rules in DBMS
• All stored data in a database or an application must be physically independent to access the
database.
• If data is updated or the physical structure of the database is changed, it will not show any effect on
external applications that are accessing the data from the database.
• It is similar to physical data independence. It means, if any changes occurred to the logical level
(table structures), it should not affect the user's view (application).
• For example, suppose a table either split into two tables, or two table joins to create a single table,
these changes should not be impacted on the user view application.
Codd Rules in DBMS
• A database must maintain integrity independence when inserting data into table's cells using the
SQL query language.
• All entered values should not be changed or rely on any external factor or application to maintain
integrity.
• The distribution independence rule represents a database that must work properly, even if it is
stored in different locations and used by different end-users.
• Suppose a user accesses the database through an application; in that case, they should not be aware
that another user uses particular data, and the data they always get is only located on one site.
Codd Rules in DBMS
• The non-submersion rule defines RDBMS as a SQL language to store and manipulate the data in the
database. If a system has a low-level or separate language other than SQL to access the database
system, it should not subvert or bypass integrity to transform data.