Is it a good practice to implement aggregate routes in Entity Framework 4?

Posted by Kohan on Stack Overflow See other posts from Stack Overflow or by Kohan
Published on 2010-05-24T09:50:24Z Indexed on 2010/05/24 13:21 UTC
Read the original article Hit count: 279

Having just started working on a new project using Entity Framework 4, I spoke to some of the other team that use NHibernate for advice. They implement aggregate routes on their entities, so instead of adding an order through the orders entity, they would add it through customer.order by having an addOrder method on customer.

This is the approach I have taken but I am, alas, running into problems. These are issues that I hope to work out, but it got me thinking ... Is this a good way to work or am I fighting an uphill battle unnecessarily?

© Stack Overflow or respective owner

Related posts about database

Related posts about entity-framework