数据库设计ChapDatabaseDesign演示文件修改版.pptVIP

Example: Map Class Behavior to Stored Procedures Class Candidate Operations getTuition addSchedule getSchedule deleteSchedule getStudentID getName getAddress Example: Map Class Behavior to Stored Procedures Associations between two persistent objects are realized as foreign keys to the associated objects. A foreign key is a column in one table which contains the primary key value of the associated object. Assume we have the above association between Course and CourseOffering. When we map this into relational tables, we get a Course table and a Course Offering table. The Course Offering table will have columns for attributes listed, plus an additional Course_ID column which contains foreign-key references to the primary key of associated rows in the Course table. For a given Course Offering, the Course_ID column will contain the identifier of the Course with which the Course Offering is associated. Foreign keys allow the RDBMS to join related information together. Note: the Number attribute of the Course class is a String. For optimal performance, it is best to convert this to a number in the database schema (queries and joins work faster on numbers than strings, since number comparisons are faster in general than string comparisons). Aggregation is also modeled using foreign key relationships. Assume we have the above aggregation between Student and Schedule. (Note: This is modeled as a composition, but remember that composition is a non-shared aggregation). When we map this into relational tables, we get an Student table and a Schedule table. The Schedule table will have columns for attributes listed, plus an additional column for Student_ID which contains foreign-key references to associated rows in the Student table. For a given Schedule, the Student_ID column will contain the Student_ID of the Student that the Schedule is associated with. Foreign keys allow the RDBMS to join related information together. In addition, to provide referential integrity i