I've always taken a data centric approach to web apps, and so the paradigm change involved when taking a pure OO approach using ORMs is still not completely natural to me, and evey now and then something ostensibly simple is not obvious.
Can someone please point me into the right direction of how to correctly model this situation in an ORM (Specifically NHibernate).
The situation: There are many Users, Many Items, users may rate Items.
In a data centric/relational approach it would look like this (and be very easy!):
- Items Table
ItemID
ItemName
- UserRatings Table
UserID
ItemID
Rating
- Users Table
UserID
UserName
If you want to find out what rating your logged in user gave for a particular item, you just do a joined query.
However, it's not obvious to me how to model this in a OO way when using an ORM. I beleive I need three domain classes: Item, UserRating, and User. Presumably I also need a collection of UserRatings in the Items class, and a collection of UserRatings in the User class. But how do I navigate to the corect UserRating, from a particular item which I have loaded (and of course this UserRating must be the one related to the user I'm interested in).
Can anyone clarify this for me?
Thanks