0% found this document useful (0 votes)
79 views8 pages

EF Codd Rule

E.F. Codd introduced 13 rules in 1985 to define what constitutes a true relational database management system (RDBMS). These rules cover various aspects of database functionality, including data access, integrity, and independence from physical and logical changes. Following these rules ensures that a database adheres to the principles of the relational model, providing a systematic approach to data management.

Uploaded by

shubham.soni
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
79 views8 pages

EF Codd Rule

E.F. Codd introduced 13 rules in 1985 to define what constitutes a true relational database management system (RDBMS). These rules cover various aspects of database functionality, including data access, integrity, and independence from physical and logical changes. Following these rules ensures that a database adheres to the principles of the relational model, providing a systematic approach to data management.

Uploaded by

shubham.soni
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 8

EF Codd Rule

Introduction of Relational Model

• 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

• Rule 0: The Foundation Rule:

• The database must be in relational form. So that the system can handle the database through its
relational capabilities.

• Rule 1: Information Rule :

• A database contains various information, and this information must be stored in each cell of a table
in the form of rows and columns.

• Rule 2: Guaranteed Access Rule

• 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.

• Rule 3 : Systematic Treatment of Null Values

• 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

• Rule 4: Active/Dynamic Online Catalog based on the relational model:

• 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.

• Rule 5: Comprehensive Data SubLanguage Rule:

• 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

• Rule 6: View Updating Rule:

• 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

• Rule 8: Physical Data Independence Rule:

• All stored data in a database or an application must be physically independent to access the
database.

• Each data should not depend on other data or an application.

• 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.

• Rule 9: Logical Data Independence Rule:

• 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

• Rule 10: Integrity Independence Rule :

• 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.

• It is also helpful in making the database-independent for each front-end application.

• Rule 11: Distribution Independence Rule:

• 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

• Rule 12: Non Subversion Rule :

• 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.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy