Names of database relations, their database attributes and value domains, together with applicable database integrity constraints.
A decomposition in which the database integrity constraints can be enforced using constraints on individual component database relations, without computing their relational join.
A decomposition of a relational schema whose component relational projections always reconstruct the original database relation by natural join, without extra database tuples.
For database tuples agreeing on , requires the combinations obtained by swapping their values on and on the remaining database attributes to occur too. A functional dependency implies the corresponding multivalued dependency; complementation exchanges with the remaining database attributes. A multivalued dependency is trivial if or is the full relational schema.
The set of database attributes determined by under given functional dependencies. Start from and repeatedly add the right-hand side of each functional dependency whose left-hand side is already included.
A database integrity constraint requiring values of specified database attributes to occur in a referenced identifier of another database relation.
An inclusion-minimal superkey: removing any of its database attributes destroys the superkey property. Minimal means inclusion-minimal, not necessarily smallest in size.
The candidate key selected as the principal identifier for database tuples of a database relation.
A condition required of every legal instance of a relational schema.
A named component of a database tuple.
One record of a database relation, assigning a value to each database attribute.
A set of database tuples with the same named database attributes; unlike an SQL result without duplicate elimination, a mathematical database relation has no repeated database tuples.

Articles by others on the same topic (0)

There are currently no matching articles.