Scribd
Upload
294 views3 pages

Codd Rules of Converting Dbms 2 Rdbms

The document summarizes Codd's 12 rules for relational databases. The rules require that: 1) all data is represented as values in tables, 2) data can be logically accessed via table name, primary key and column name, 3) null values are supported to represent missing or unknown data. The database schema is also defined internally using the same relations as regular data.

Uploaded by

parulkak
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
294 views3 pages

Codd Rules of Converting Dbms 2 Rdbms

The document summarizes Codd's 12 rules for relational databases. The rules require that: 1) all data is represented as values in tables, 2) data can be logically accessed via table name, primary key and column name, 3) null values are supported to represent missing or unknown data. The database schema is also defined internally using the same relations as regular data.

Uploaded by

parulkak
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

Codd's Rules

Rule 1 : The information Rule.


"All information in a relational data base is represented explicitly at the logical level and in exactly one way - by values in tables." Everything within the database exists in tables and is accessed via table access routines.

Rule 2 : Guaranteed access Rule.


"Each and every datum (atomic value) in a relational data base is guaranteed to be logically accessible by resorting to a combination of table name, primary key value and column name." To access any data-item you specify which column within which table it exists, there is no reading of characters 10 to 20 of a 255 byte string.

Rule 3 : Systematic treatment of null values.


"Null values (distinct from the empty character string or a string of blank characters and distinct from zero or any other number) are supported in fully relational DBMS for representing missing information and inapplicable information in a systematic way, independent of data type." If data does not exist or does not apply then a value of NULL is applied, this is understood by the RDBMS as meaning non-applicable data.

Rule 4 : Dynamic on-line catalog based on the relational model.


"The data base description is represented at the logical level in the same way as-ordinary data, so that authorized users can apply the same relational language to its interrogation as they apply to the regular data." The Data Dictionary is held within the RDBMS, thus there is no-need for off-line volumes to tell you the structure of the database.

Rule 5 : Comprehensive data sub-language Rule.


"A relational system may support several languages and various modes of terminal use (for example, the fill-in-the-blanks mode). However, there must be at least one language whose statements are expressible, per some well-defined syntax, as character strings and that is comprehensive in supporting all the following items

Data Definition View Definition Data Manipulation (Interactive and by program). Integrity Constraints Authorization.

Every RDBMS should provide a language to allow the user to query the contents of the RDBMS and also manipulate the contents of the RDBMS.

Rule 6 : .View updating Rule


"All views that are theoretically updatable are also updatable by the system." Not only can the user modify data, but so can the RDBMS when the user is not logged-in.

Rule 7 : High-level insert, update and delete.


"The capability of handling a base relation or a derived relation as a single operand applies not only to the retrieval of data but also to the insertion, update and deletion of data." The user should be able to modify several tables by modifying the view to which they act as base tables.

Rule 8 : Physical data independence.


"Application programs and terminal activities remain logically unimpaired whenever any changes are made in either storage representations or access methods." The user should not be aware of where or upon which media data-files are stored

Rule 9 : Logical data independence.


"Application programs and terminal activities remain logically unimpaired when informationpreserving changes of any kind that theoretically permit un-impairment are made to the base tables." User programs and the user should not be aware of any changes to the structure of the tables (such as the addition of extra columns).

Rule 10 : Integrity independence.


"Integrity constraints specific to a particular relational data base must be definable in the relational data sub-language and storable in the catalog, not in the application programs."

If a column only accepts certain values, then it is the RDBMS which enforces these constraints and not the user program, this means that an invalid value can never be entered into this column, whilst if the constraints were enforced via programs there is always a chance that a buggy program might allow incorrect values into the system.

Rule 11 : Distribution independence.


"A relational DBMS has distribution independence." The RDBMS may spread across more than one system and across several networks, however to the end-user the tables should appear no different to those that are local.

Rule 12 : Non-subversion Rule.


"If a relational system has a low-level (single-record-at-a-time) language, that low level cannot be used to subvert or bypass the integrity Rules and constraints expressed in the higher level relational language (multiple-records-at-a-time)." The RDBMS should prevent users from accessing the data without going through the Oracle data-read functions. In Rule 5 Codd stated that an RDBMS required a Query Language, however Codd does not explicitly state that SQL should be the query tool, just that there should be a tool, and many of the initial products had their own tools, Oracle had UFI (User Friendly Interface), Ingres had QUEL (QUery Execution Language) and the never released DB1 had a language called sequel, the acronym SQL is often pronounced such as it was sequel that provided the core functionality to SQL. Even when the vendors eventually all started offering SQL the flavours were/are all radically different and contained wildly varying syntax. This situation was somewhat resolved in the late 80's when ANSI brought out their first definition of the SQL syntax. This has since been upgraded to version 2 and now all vendors offer a standard core SQL, however ANSI SQL is somewhat limited and thus all RDBMS providers offer extensions to SQL which may differ from vendor to vendor.

Common questions

Powered by AI

Codd's Rule 8 ensures that changes in storage mechanisms do not affect user interactions by providing physical data independence. This means that modifications to storage representations or access methods do not impair application programs and terminal activities, thereby abstracting the physical data layer from users who interact with the database only at the logical or application level .

Codd's Rule 1, the Information Rule, implies that all data within a relational database is represented at the logical level in exactly one manner—through values in tables. This indicates a standardized approach for data representation, ensuring that all information is stored in an organized, accessible format through table structures .

Enforcement of integrity constraints in Codd's Rule 10 is critical because it ensures that the database automatically upholds data validity, preventing the entry of invalid data. This is distinct from application-level enforcement, which might be circumvented by bugs, as integrity is managed within the RDBMS itself, guaranteeing that constraints are consistently applied regardless of application state or correctness .

The concept of distribution independence in Codd's Rule 11 implies that a relational DBMS can operate across multiple systems and networks while users perceive the tables as if they are local. This allows for data distribution and redundancy without impacting user interaction, as operations and data access are seamlessly integrated despite the underlying physical distribution .

The Dynamic Online Catalog described in Codd's Rule 4 provides advantages by storing database descriptions at the logical level, allowing authorized users to query metadata using the same relational language as regular data. This integration eliminates the need for separate offline schema volumes, facilitating easier and more consistent access to database structures and enhancing the efficiency of database administration .

Codd's Rule 5 ensures a relational DBMS supports diverse data operations by mandating the presence of at least one language with a well-defined syntax for comprehensive data manipulation tasks. This includes data definition, view definition, data manipulation, integrity constraints, and user authorization, thus ensuring that the relational database can fully support interactive and programmed data operations .

Codd's Rule 12 addresses security risks by ensuring that low-level access languages cannot subvert integrity constraints established by higher-level relational languages. By restricting direct, record-at-a-time access methods, the RDBMS mitigates the potential for unauthorized access and manipulation of data, thus maintaining a secure system where integrity rules are consistently enforced .

Codd's Rule 7 impacts data manipulation by allowing high-level operations such as insert, update, and delete to be performed not only on single data items but also on entire base or derived relations as single operands. This capability enhances efficiency by enabling complex operations on multiple tables through a single command, aligning with the goal of giving end-users powerful yet simple tools for data manipulation .

Codd's Rule 3 facilitates the handling of missing and inapplicable data by supporting null values, which are distinct from empty strings or zero. This allows relational database management systems to systematically represent missing or inapplicable data, independent of data type, thus preserving data integrity without misinterpreting absent or irrelevant data .

The evolution of SQL reflects Codd's Rule 5 by serving as a comprehensive data sub-language with a well-defined syntax for various database operations like data manipulation, integrity constraints, and authorization. Although Codd did not mandate SQL specifically, the eventual standardization of SQL by ANSI aligns with the principle of providing a single, comprehensive language to interact with relational databases effectively. The extension and adaptation of SQL by various vendors show its flexibility and foundational alignment with Codd's principles of supporting diverse operational requirements .

You might also like