Subscribe to:
Post Comments (Atom)
skip to main |
skip to sidebar
The aim of this Blog is to provide a forum for raising questions and discussing the paper on Foreign Keys.
Download the Discussion Paper from here.
http://www.eternal-donut.com/downloadp/foreign_key_discussion_kratochvil_v11.pdf
The only rule that I ask is that you read the whole paper (in its entirety) before making any comments.
Eternal Donut Blog
Blog Archive
About this Paper
- Marcelle Kratochvil
- Canberra, ACT, Australia
- Marcelle Kratochvil is CTO for Piction and is the Oracle ACE Director for all data/any data. She has extensive experience in the business of setting up and manging multimedia sites, having setup over 30 in the last 5 years. Marcelle has been using the Oracle database for the past twenty years and originally began using Oracle with V5 on MVS and VMS. She has been awared PL/SQL Developer of the year in 2004, and has won awards for development of a shipping system and state government digital asset management. Over the last ten years Marcelle has been involved in the core development of Piction and has been involved in the installation and management of this product in countries around the world. She has extensive experience in Oracle Database Administration, including the performance of large databases, network management and application development. She has been a regular presenter at OpenWorld and first presented at OpenWorld in 1993. She recently presented at OpenWorld 2010 and has done internal presentation to Oracle. Marcelle is also an 11g Beta Tester and does tuning trouble shooting for Government Departments and commercial organisations.
Posts
Object/Relational is a definite improvement for two reasons that I can name off the bat. First, it allows me to interface better with Object Oriented application development tools. Second, it lets me define my own complex datatypes - telephone number and address types come to mind. However, Relational is NOT obsolete. In fact, I'd rather use Object Views of Relational tables for interfacing with Object Oriented applications, than Object Tables.
ReplyDeleteLet me give you an example from a system I worked on. It is a Purchase Request(PR)/Purchase Order(PO) system. PRs and POs as objects are very similar. You can think of each as consisting of information related to the entire PR or PO, such as the customer account number, plus information related to each item being ordered - what, how many, cost of each. If that was all, Object Relational would be fine. However, items from one or more PRs can be combined to create one or more items in one or more POs. You have to maintain these many to many relationships between PR items and PO items, because when the orders are filled, the items have to be distributed back to the people who requested them. This would be difficult to do if the items weren't in separate relations from the parent PR and PO records.