Relations between objects are not limited to an object that keep a reference to another object (as seen in part 2), but I can have an object that contains a list of other objects. This is the classic RDBMS rough equivalent of the One-To-Many relation. I decided that my Warrior can carry a certain number of items, so I defined an Item class and a property on Warrior class to hold reference to a list of Items.
This is a standard implementation of a property that permits me to establish that a Warrior can have a list of Items. In the Getter part I use lazy initialization, so I can simply add an IList<Item> from external code, or I can simply let the object auto-initialize a standard list for me. This is the code that actually adds some item to a Warrior.
Again I want to point out that I did not make any other changes to the BattlefieldContext or to something related to persistence, I just defined the Item class and the Items property on the Warrior class, but Iâ€™m able to save everything to the database without writing any other line of code. Here is the query generated by EF.
Figure 1: Generated query to insert a warrior with two items.
This is the Database Schema that EF created to persist my objects.
Figure 2: The database schema to persist Warrior and Items
As you can see, EF created the Warrior_id column on the Items table to be able to keep the relation between items and warriors.
I want to strongly point out that this is nor DDD nor Domain Modeling, Iâ€™m simply using EF4.1 like a Super Dataset, to avoid writing CRUD. My primary reason for this little tutorial is moving people from HandWritten SQL code or from old style Dataset to something more flexible and more object oriented.
Tags: Entity Framework