PATH
WebObjects 4.0 Documentation >
EOF Developer's Guide
Top
Entity-Relationship Modeling
A database server stores data in the structures that it defines: A relational database uses tables to store data, an object-oriented database uses objects, a file system uses files, and so on. The Enterprise Objects Framework uses the terminology of Entity-Relationship modeling (or E-R modeling) to describe a server's data structures in a way that allows those data structures to be mapped to enterprise objects.
Entity-Relationship modeling isn't unique to the Enterprise Objects Framework; it's a popular discipline with a set of rules and terms that are documented in database literature. The Enterprise Objects Framework uses a modified version of the traditional rules of E-R modeling.
When your data store is a relational database, you can use the EOModeler application to specify the mapping between the database data and your enterprise objects. The model file you produce using EOModeler describes the server's data structures in terms that the Enterprise Objects Framework can understand. Note that if you're working with a data store other than a database, you must create your own data structures to map the server's data to your enterprise objects.
This chapter presents the E-R terms and concepts as they are used by the Framework. For instructions on putting these concepts into practice, see the book Enterprise Objects Framework Tools and Techniques.
Modeling Objects
Entities and Attributes
Names and the Data Dictionary
Attribute Data
The Primary Key
Relationships
Relationship Directionality
Naming Relationships
Relationship Keys
Relationship Cardinality
Bidirectional Relationships
Reflexive Relationship
Flattened Attributes
First Section