12 Codd's Rules

By -

Codd has given 12 rules , which every database has to follow to become a relational dtabase.

Rule 0: The system must qualify as relational, as a database, and as a management system.

For a system to qualify as a relational database management system (RDBMS), it system must use its relational facilities (exclusively) to manage the database.

Rule 1: The information rule:

All information in the database is to be represented in one and only one way, namely by values in column positions within rows of tables.

Rule 2: The guaranteed access rule:

All data must be accessible. This rule is essentially a restatement of the fundamental requirement for primary keys. It says that every individual scalar value in the database must be logically addressable by specifying the name of the containing table, the name of the containing column and the primary key value of the containing row.

Rule 3: Systematic treatment of null values:

The DBMS must allow each field to remain null (or empty). Specifically, it must support a representation of "missing information and inapplicable information" that is systematic, distinct from all regular values (for example, "distinct from zero or any other number", in the case of numeric values), and independent of data type. It is also implied that such representations must be manipulated by the DBMS in a systematic way.

Rule 4: Active online catalog based on the relational model:

The system must support an online, inline, relational catalog that is accessible to authorized users by means of their regular query language. That is, users must be able to access the database's structure (catalog) using the same query language that they use to access the database's data.

Rule 5: The comprehensive data sublanguage rule:

The system must support at least one relational language that
  1. Has a linear syntax
  2. Can be used both interactively and within application programs,
  3. Supports data definition operations (including view definitions), data manipulation operations (update as well as retrieval), security and integrity constraints, and transaction management operations (begin, commit, and rollback).

Rule 6: The view updating rule:

All views that are theoretically updatable must be updatable by the system.

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

The system must support set-at-a-time insert, update, and delete operators. This means that data can be retrieved from a relational database in sets constructed of data from multiple rows and/or multiple tables. This rule states that insert, update, and delete operations should be supported for any retrievable set rather than just for a single row in a single table.

Rule 8: Physical data independence:

Changes to the physical level (how the data is stored, whether in arrays or linked lists etc.) must not require a change to an application based on the structure.

Rule 9: Logical data independence:

Changes to the logical level (tables, columns, rows, and so on) must not require a change to an application based on the structure. Logical data independence is more difficult to achieve than physical data independence.

Rule 10: Integrity independence:

Integrity constraints must be specified separately from application programs and stored in the catalog. It must be possible to change such constraints as and when appropriate without unnecessarily affecting existing applications.

Rule 11: Distribution independence:

The distribution of portions of the database to various locations should be invisible to users of the database. Existing applications should continue to operate successfully :
  1. when a distributed version of the DBMS is first introduced; and
  2. when existing distributed data are redistributed around the system.

Rule 12: The nonsubversion rule:

If the system provides a low-level (record-at-a-time) interface, then that interface cannot be used to subvert the system, for example, bypassing a relational security or integrity constraint.

Comments

Post a Comment

Popular posts from this blog

Progress 4GL interview questions for QAD technology

By -
1.        What is “No-undo” in the variable declaration? 2.        What are the different .pf parameters 3.        What are the different types of  locks in progress? Explain with example. If a record is locked Exclusively, can a shared lock be provided over the same? 4.        What are different type of procedures in progress? Can internal procedure call other internal procedure? If yes how? If no why no? Can external procedure call internal procedures? 5.        How is array defined in progress? What is the limit of extent for progress? Can we create 2 dimensional / multi dimensional arrays in progress / How? If no then how can we achieve the same? 6.        What are browses? 7.        What are queries? 8.        Can we call excel application from progress? How? 9.        What is the difference between can-find and find? 10.     What are the different types of triggers available in progress? Name few database level triggers. 11.     What are the different type
Read more

QAD interview questions for SE and Eb2 version

By -
1.       What is the difference between WO close and WO accounting close. 2.       What are the different types of transaction types in mfg-pro 3.       What is tag count when it is used 4.       Explain the purchase cycle 5.       What is the difference between the WO module and Repetitive  module. 6.       Explain the Payment cycle 7.       Explain the Sales Cycle 8.       What is a schedule order 9.       Explain GTM why and where it can be used 10.   How can u ensure that the supplier is given a schedule on a particular day of the week say only on Monday. 11.   What is MRP .What are the different types of MRP 12.   Can the  status of the the material can be changed 13.   What are financial transactions passed when you do voucher and payments. 14.   What are the transaction  passed when the payment is made 15.   The financial transaction passed when the sales  order is  updated. 16.   What are the primary input for MRP explain  in details 17.   Expl
Read more

Use of API in QAD EE

By -
/*Sample API Program to create currency in QAD EE*/ {us/mf/mfdtitle.i} {us/bbi/gplabel.i} {us/wb/wbrp01.i}         {us/gl/glsec.i} {us/gp/gpuid.i} {proxy/bcurrencydef.i } /* ======== FOR API ========= */ DEFINE VARIABLE viReturn                     AS INTEGER     NO-UNDO. DEFINE VARIABLE ilReturnDataset              AS LOGICAL     NO-UNDO. DEFINE VARIABLE ilPartialUpdate              AS LOGICAL     NO-UNDO. DEFINE VARIABLE icPartialUpdateExceptionList AS CHARACTER   NO-UNDO. DEFINE VARIABLE ocPrimaryKey                 AS CHARACTER   NO-UNDO. DEFINE VARIABLE ocRowid                      AS CHARACTER   NO-UNDO. DEFINE VARIABLE oiDraftInstance              AS INTEGER     NO-UNDO. DEFINE VARIABLE ocPrimaryKeyName             AS CHARACTER   NO-UNDO. DEFINE VARIABLE vho                          AS HANDLE. DEFINE VARIABLE oiReturnStatus               AS INTEGER     NO-UNDO. empty temp-table tCurrency. for first RoundingMethod no-lock where RoundingMethodCode = "
Read more