Hand in a listing of your programs and scripts showing them working. You should demonstrate that the programs had their intended effect by querying (before and after) some relation of your PDA that was changed by the program. These queries may be included in the file that holds your PL/SQL programs for convenience.
Hand in listings of your code and scripts showing them called at least once each. Also, show in the script the results of queries that demonstrate the functions have had their intended effect.
Hand in your code and a script showing the triggers declared. Also, the script should show, for each trigger, the effect of two database modifications. One modification should trigger the trigger, and the other not. Show in the script queries that demonstrate that the trigger has an effect in the first case and not in the second.
Consider a relation R(A, B, C) containing four tuples as follows. List all nontrivial multivalued dependencies that hold on R .
A | B | C |
---|---|---|
1 | 2 | 3 |
1 | 2 | 4 |
5 | 2 | 3 |
5 | 2 | 6 |
Note: in general it is not possible to determine that a dependency of any sort holds, just by looking at one instance of a relation. However, we can still ask and answer the question of what the possible dependencies are, given one instance.
Consider a database for a university, including information about courses, professors, departments, academic years (quarters), etc.