This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hi, while alle other Entity association are shown, the value objects associations are not considered by the filter. -Sörnt
|
|
|
|
|
Addressed in the next nightly build. |
|
|
|
|
Actually... I may have misunderstood you. I've changed it to show value objects associated with any entities that are part of the aggregate. Did you want it to show only value object associations that are part of the aggregate (and hide value object associations that are not part of the aggregate)? That may be a little trickier but it sounds more informative... let me know... |
|
|
|
|
My understanding of the aggregate filter is to get an idea of the loading graph. Thanks for having a look at that! |
|
|
|
|
Okay, I have some good news and some bad news. The good news is that I have made this change and it will be in the next nightly build. The bad news is that it operates at a value object type level, not at an association level. That is, although it will show the value type only if it is eager loaded through the current aggregate, it will show all associations from visible entities to the value type, not just the one(s) that cause the eager load. For example, if you have an Employee entity and a Currency value type, and the Employee has both a Salary which is part of the A aggregate and a Bonus which is part of the B aggregate, and you apply the @A filter, then you will see the Currency type and Salary member as expected, but you will also see the Bonus member even though Bonus is lazy in the A aggregate. Put another way, we can't currently hide individual connections, so showing Employee and Currency results in showing all connections between them, not just the Salary connection. To mitigate this, member value object associations will now show aggregates in the same way as entity associations (if the relevant Tools Options setting is selected). So even in the situation above you will have a way of seeing that Bonus is not part of the eager load. |
|
|
|
