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
|
I’m finding that using Aggregates for eager loading is becoming a little awkward to manage. We require a few of them. They are kind of hidden away in the model and you have to sort of poke around to find them. It’s hard to remember what aggregates you’ve setup and it’s going to be even harder for others to see how they’ve been setup, especially when using them to cascade the loading of other entities and fields. Perhaps you have a few tips or best practices you could share with us? Also is it possible to use type safe values instead of strings when naming and using aggregates? Finally why does the lightspeed engine only allow one aggregate to be used per query? |
|
|
For seeing aggregates on the design surface: see http://www.mindscapehq.com/blog/index.php/2009/05/27/visualising-eager-load-graphs-in-the-lightspeed-designer/ and http://www.mindscapehq.com/blog/index.php/2011/02/07/everything-you-wanted-to-see-in-the-lightspeed-designer-but-ran-out-of-screen-space-for/ (this works for associations too in current nightly builds). We don't have support for 'safe' aggregate names or multiple aggregates in a query at the moment, but they are on the wish list -- thanks for the feedback which helps us prioritise! |
|