The right frame of the Model Editor shows the Movie's relationships as well as its attributes.
Your model's Movie entity might have a different name than the movieRoles relationship shown above. That's because the wizard created your relationship, and the relationship's name is dependent on the adaptor the wizard used. Adaptors don't all have the same naming convention for to-many relationships. For example, the Oracle adaptor names Movie's relationship movieRoleArray instead of movieRoles.
If your Movie entity doesn't have a movieRoles relationship, it means that the database server's schema information for your database didn't have enough information for the wizard to create them. You need to create them by hand now. The next several steps explain how.
A new relationship named "Relationship" is added in the table view at the bottom of the Model Editor. The new relationship is already selected.
EOModeler automatically renames the relationship based on the name of the destination entity. For example, after connecting a to-many relationship from Movie to MovieRole, EOModeler names the relationship "movieRoles." To-one relationships are named with the singular form of the destination entity's name. For example, EOModeler names the inverse to-one relationship (from MovieRole to Movie) "movie."
If the wizard created your relationship and used a name other than "movieRoles," consider renaming the relationship. The rest of this tutorial assumes that your relationships are named using EOModeler's naming convention.
A to-one relationship named "movie" in the MovieRole entity where:
A to-one relationship named "talent" in the MovieRole entity where:
A to-many relationship named "movieRoles" in the Talent entity where:
You can also use the Diagram View to edit your model. Double-click an attribute or relationship to change its name. To create a relationship and its inverse, Control-drag from the relationship's source attribute to its destination attribute.
Table of Contents Next Section