2.3 Relational Rules
(1)All pure relational products obey this rule (2) The reason why this is not permitted. Difficulty in storing the data, waste space. (3) Solution to this problem. Partition See P34 (4) In OR model, Figure 2.3 is OK.
A problem
For example, we want to manage the information of students, courses and relationship between them. In a file a system, how to solve the problem?
2.1 An Example DB
(5) Note that table is unrealistically small: more columns (name, straddr, contact, timestamp for orders), more rows, more tables (keep track of billing, salaries, taxes)
2.2 Terminology
Definition 2.1 Cartesian Product. The
Cartesian Product of a sequence of k sets S1, S2, …., Sk is represented by S1× S2 ×… × Sk And consist of all the possible k-tuple (e1, e2, …, ek), Where e1 is any element in S1, e2 is any element in S2, …, ek is any element in Sk