Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


If you did everything well, the list of attributes should look like this:

Image RemovedImage Added

You will notice that the attributes have a column with a lock in it. When a lock is present, it will use the value of that attribute for UPDATE ... WHERE attribute = '' statement. This is to do optimistic locking, aka to prevent data conflict when the data object was modified by two different users. Using timestamps for optimistic locking is not a good idea because for certain RDBMS, the value can be different because of milliseconds, so remove the locks on the creationDate attribute. The final list should look like this:

Image Added

Next step is to create the Author entity. Create a new entity with Author at its name (and also as the table name), and for the class name, use The attributes for this entity are:


Final list of attributes should look like this:

Image Removed 

Now, it's time to link the two entities together. An Author can have multiple blog entries, and a BlogEntry can only have one author. To create the relationship (the join), right-click on Author and select New Relationship. On your right, select BlogEntry in the list. On your left, select to many BlogEntries, and on your right, select to one Author. Now, in BlogEntry, we need to store the primary key of the author so that we can make the join. The relationship builder allow us to add that attribute, so make sure and a new foreign key named is checked (it is checked by default). The Create Relationship pane should look like this: