Software Engineering Stack Exchange is a question and answer site for professionals, academics, and students working within the systems development life cycle. It only takes a minute to sign up.
Sign up to join this community
As far as I understand, the domain model should not know about the persistence layer. But then... How can I deal with removing element that are dependant of a father object?
For example, in my domain, if I have a ShoppingBasket with Products, and I want to remove a Product. I can remove the Product in my Domain Model. But how will I get my persistence layer to be aware that a Product must be deleted (i.e. how do I get the corresponding product relashionship removed from the database)?
Usually, in situations like this, there is an object that maps the associated objects to each other. In this case, it would be a BasketItem object. It would look something like this:
public class BasketItem
{
public int BasketID;
public int ProductID;
public int Quantity;
}
Removal of the item from the basket is a simple matter of removing the appropriate BasketItem object.
This is basic database design, which is why it's not obvious. Database design is not always taught in "class first" paradigms, which is unfortunate.
