difference between table level constraint and column level and
advantages of table level constraint
Answers were Sorted based on User's Feedback
Answer / santosh kumar
Let me explain both sides of the coin bit more clearly.
Table level Constraint
===========================
1. Constraints are defined separately after the columns are defined.
2. While defining constraints at this level constraint name must be provided
3. Not null constraints can't be defined at this level.
4. Composite keys can be defined at this level only.
A table level constraint can see every column in the table.
Column level Constraint
===========================
1. Constraints are defined along with the columns.
2. So constraint name is not required.
3. Not null constraints can be defined at this level only(NOT NULL constraint can only apply to one column).
4. Composite keys can't be defined at this level .
5. Column level constraint is more clear syntactically and more meaningful.
A column level constraint has scope only to the column it is defined on.
The major difference between the two constraint is the scope. So far as the use of constraints (validating proper data) is concerned they are pretty much the same.
Any column level constraint (exception: not null) can be expressed at the table level - but the opposite is not true.
Go for a column level constraint if the constraint is in fact a column constraint else use a table constraint.
It is recommended to always use a column constraint if the constraint applies just to the column (and NOT a table constraint if it only applies to a single column) - you can only do it at the column level.
Is This Answer Correct ? | 6 Yes | 0 No |
Answer / anil
ANS:
COLUMN LEVEL CONSTRAINT
If we provide constraint along with column while creating the table then it is column level constraint. For column level constraint a constraint name is not mandatory.
TABLE(ROW) LEVEL CONSTRAINT
If we provide constraint after providing all the columns then it is table level constraint.For table level constraint a constraint name is mandatory.
Advantage of table level constraint:
We can create composite PK and composite FK in table level constraints but we cant create these in column level constraints.
Example:
CREATE TABLE oracle_tab
(
ord_id NUMBER,
pid NUMBER,
qty NUMBER(2),
ord_dt DATE NOT NULL, /*column level constraint(cant be created as table level constraint)*/
price NUMBER(9,1) DEFAULT 0, /*column level constraint(cant be created as table level constraint)*/
CONSTRAINT ord_pk PRIMARY KEY(ord_id,pid), /*table level(can be created either as table level constraint or column level)*/
CONSTRAINT ord_fk FOREIGN KEY(pid) REFERENCES products(pid),/*table level(can be created either as table level constraint or column level)*/
CONSTRAINT ord_ch CHECK(qty>0) /*table level(can be created either as table level constraint or column level)*/
);
Is This Answer Correct ? | 4 Yes | 1 No |
Answer / selvi
Column level constraint can not refer other columns or sysdate, UID, currVal, nextVal or rownum, and this is limitation of column level constraint over table level constraint.
Is This Answer Correct ? | 1 Yes | 2 No |
Answer / sravya
column level contains only one column whereas tablelevel contains group of columns
Is This Answer Correct ? | 0 Yes | 1 No |
If 100 tables are there in user_tables.I want to find in which table zero records are there with table name.Is it possible?
what is the difference between a web-garden and a web-farm? : Sql dba
I Defined SP1, Sp2 (sp=StoreProcedures)In Package Specification but I Implemented Sp1, sp2, sp3, sp4, sp5 then What type of Error You will find????
why sql is used as interpreter frequently rather than a compile?
Is pl sql and postgresql same?
what is single byte over head in oracle..?
Is sqlexception checked or unchecked?
Explain ddl statements in pl/sql?
what are the advantages and disadvantages of views in a database? : Sql dba
what is the difference between mysql_fetch_array and mysql_fetch_object? : Sql dba
how to increment dates by 1 in mysql? : Sql dba
What is bitemporal narrowing?