Q. The key which specifies that two different tuples cannot have the same value is classified as

View solution

Q. The format or data type must be specified for

View solution

Q. In a relation schema, each key of schema having more than one key is classified as

View solution

Q. In the data model schemas, the constraints that are can not be expressed directly are classified as

View solution

Q. The cardinality in relational data model is considered as

View solution

Q. The constraint violated when the given value of attribute is not included in the corresponding domain is

View solution

Q. If two or more constraints are violated by using insert operation then by default the

View solution

Q. In the data model, the inherent constraints are classified as

View solution

Q. The multi-valued dependencies and functional dependencies are classified as category of

View solution

Q. The model in which the multi-valued and composite attributes is considered as

View solution

Q. The type of constraint in which value of each attribute (X) must be an indivisible value from domain (X) is classified as

View solution

Q. The constraints which deals with the changes in the database are classified as

View solution

Q. The multivalued dependencies used to develop relational design theory of database is classified as

View solution

Q. In the data model schemas, the constraints that are expressed directly are classified as

View solution

Q. In relational database schemas, the transition constraints are also known as

View solution

Q. A row of table in relational model terminology is classified as

View solution

Q. The constraint which is used to specify the consistency in two or more relations among tuples is classified as

View solution

Q. The ordered list of all the n-values is classified as

View solution

Q. The state in which the database follows all the integrity constraints is classified as

View solution

Q. The column header of table in relational model terminology is classified as

View solution