Appendix G Object-Oriented Databases
- Charleswest
- Rating : 0
- Grade : No Rating
- Questions : 0
- Solutions : 123
- Blog : 0
- Earned : $0.00
Discussion Focus Because an OO model necessarily forces the student to come to terms with some very abstract notions, begin the discussion by pointing out the practical benefits of system modularity; then carefully delineate the OO features that almost inevitably lead to modularity. At this point, students should be familiar with the relational model, so show how the OO model handles attributes and demonstrate that: 1. Although the term "object" in a relational environment is sometimes used as synonymous with "entity," an object in an OO environment contains much more than attributes. Use Figure G.2 to show that the object contains both data and methods: Every operation to be performed on the object is implemented by a method! And the methods are carried along with the object, thus producing modularity! 2. An OO attribute (not its value!) can reference one or more other objects. 3. Unlike the relational model, the OO model does not need a JOIN to link tables through their common attribute values. 4. There is quite a difference between the relational model's primary key and the OO model's OID.
[Solved] Appendix G Object-Oriented Databases
- This solution is not purchased yet.
- Submitted On 08 Nov, 2021 11:21:28
- Charleswest
- Rating : 0
- Grade : No Rating
- Questions : 0
- Solutions : 123
- Blog : 0
- Earned : $0.00