Constraints are one of the fundamental concepts, which arrive at a very elementary stage of Database designing. Constraints are nothing but the rules on the data. This preserves the Entity integrity, Referential Integrity, and Domain Integrity of the data. While entity integrity focusses on uniqueness and NULLable property of a data, referential checks the data of a column ‘in reference to’ its parent column. Domain integrity defines a domain set for a column.
They are imposed upon the table columns, where they act as barrier for the incoming data. Once the checks are activated, only the obedient data is allowed to grab the seat. System raises the ‘Violating’ exception, if the data fails the constraint rule.
My obligations to DBANotes.com, who published the content. Read the complete paper at the below link.
http://www.dbanotes.com/database-development/understanding-oracle-11g-constraints/
Do post your feedback/comments/queries.
Saurabh
Related articles
- Why is it desirable to enforce the referential integrity rules and entity integrity rules (wiki.answers.com)
- not null enable novalidate操作注意点 (nulldb.wordpress.com)
- Big Tables, Sorts and Indexes Quiz (Candidate) (richardfoote.wordpress.com)
- Null (jonathanlewis.wordpress.com)
- Database schema navigation in Java (lukaseder.wordpress.com)
- Deadlock (jonathanlewis.wordpress.com)
culture, change, and tech 
Thanks for that awesome posting. It saved MUCH time 🙂
This is a cool page! How long have you been writing?
very nice post, keep on it