Scribd
Upload
12 views5 pages

Constraints

Uploaded by

Monalia ghosh
Copyright
© © All Rights Reserved
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
12 views5 pages

Constraints

Uploaded by

Monalia ghosh
Copyright
© © All Rights Reserved
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
You are on page 1/ 5

Constraints:

This indicates that only a particular type of data may be entered into the
database or that only a particular sort of operation can be performed on
the data inside.

Constraints thereby guarantee data accuracy in a database management


system (DBMS).

The following can be guaranteed via constraints


Data Accuracy − Data accuracy is guaranteed by constraints, which make sure that only
true data is entered into a database. For example, a limitation may stop a user from
entering a negative value into a field that only accepts positive numbers.
Data Consistency − The consistency of data in a database can be upheld by using
constraints. These constraints are able to ensure that the primary key value in one table is
followed by the foreign key value in another table.
Data integrity − The accuracy and completeness of the data in a database are ensured by
constraints. For example, a constraint can stop a user from putting a null value into a field
that requires one.

Types of Constraints in DBMS

 Domain Constraints
 Key Constraints
 Entity Integrity Constraints
 Referential Integrity Constraints
Domain Constraints: Domain constraints are guidelines that specify the acceptable values for a
certain property or field. These restrictions guarantee data consistency and aid in preventing the
entry of inaccurate or inconsistent data into the database.
 Data type constraints − These limitations define the kinds of data
that can be kept in a column. A column created as VARCHAR can
take string values, but a column specified as INTEGER can only
accept integer values.
 Length Constraints − These limitations define the largest amount
of data that may be put in a column. For instance, a column with the
definition VARCHAR(10) may only take strings that are up to 10
characters long.
 Range constraints − The allowed range of values for a column is
specified by range restrictions. A column designated as
DECIMAL(5,2), for example, may only take decimal values up to 5
digits long, including 2 decimal places.
 Nullability constraints − Constraints on a column's capacity to
accept NULL values are known as nullability constraints. For
instance, a column that has the NOT NULL definition cannot take
NULL values.
 Unique constraints − Constraints that require the presence of
unique values in a column or group of columns are known as unique
constraints. For instance, duplicate values are not allowed in a
column with the UNIQUE definition.
 Check constraints − Constraints for checking data: These
constraints outline a requirement that must hold for any data placed
into the column. For instance, a column with the definition CHECK
(age > 0) can only accept ages that are greater than zero.
 Default constraints − Constraints by default: Default constraints
automatically assign a value to a column in case no value is
provided. For example, a column with a DEFAULT value of 0 will
have 0 as its value if no other value is specified.

Key Constraints

Key constraints are regulations that a DBMS uses to ensure data accuracy
and consistency in a database. They define how the values in a table's
one or more columns are related to the values in other tables, making
sure that the data remains correct.
In DBMS, there are several key constraint kinds, including −

 Primary Key Constraint − A primary key constraint is an


individual identifier for each record in a database. It guarantees that
each database entry contains a single, distinct value—or a pair of
values—that cannot be null—as its method of identification.
 Foreign Key Constraint − Reference to the primary key in
another table is a foreign key constraint. It ensures that the
values of a column or set of columns in one table correspond to the
primary key column(s) in another table.
 Unique Constraint − In a database, a unique constraint ensures
that no two values inside a column or collection of columns are the
same.

Entity Integrity Constraints

A database management system uses entity integrity constraints (EICs) to


enforce rules that guarantee a table's primary key is unique and not null.
The consistency and integrity of the data in a database are maintained by
EICs, which are created to stop the formation of duplicate or incomplete
entries.

Each item in a table in a relational database is uniquely identified by one


or more fields known as the primary key. EICs make a guarantee that
every row's primary key value is distinct and not null. Take the
"Employees" table, for instance, which has the columns "EmployeeID" and
"Name." The table's primary key is the EmployeeID column. An EIC on this
table would make sure that each row's unique EmployeeID value is there
and that it is not null.

If you try to insert an entry with a duplicate or null EmployeeID, the


database management system will reject the insertion and produce an
error. This guarantees that the information in the table is correct and
consistent.

EICs are a crucial component of database architecture and assist


guarantee the accuracy and dependability of the data contained in a
database.

Referential Integrity Constraints

A database management system will apply referential integrity


constraints (RICs) in order to preserve the consistency and integrity of
connections between tables. By preventing links between entries that
don't exist from being created or by removing records that have related
records in other tables, RICs guarantee that the data in a database is
always consistent.

By the use of foreign keys, linkages between tables are created in


relational databases. A column or collection of columns in one table that
is used as a foreign key to access the primary key of another table. RICs
make sure there are no referential errors and that these relationships are
legitimate.

Consider the "Orders" and "Customers" tables as an illustration. The


primary key column in the "Customers" database corresponds to the
foreign key field "CustomerID" in the "Orders" dataset. A RIC on this
connection requires that each value in the "CustomerID" column of the
"Orders" database exist in the "Customers" table's primary key column.

If an attempt was made to insert a record into the "Orders" table with a
non-existent "CustomerID" value, the database management system
would reject the insertion and notify the user of an error.

Similar to this, the database management system would either prohibit


the deletion or cascade the deletion in order to ensure referential
integrity if a record in the "Customers" table was removed and linked
entries in the "Orders" table.

In general, RICs are a crucial component of database architecture and


assist guarantee that the information contained in a database is correct
and consistent throughout time.

You might also like