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
|
Jeremy - We had an exchange back in the first part of February on unwanted loading of entities based on the DataMember attribute being applied to both ends of every relationship (see the end of this post -- http://www.mindscapehq.com/forums/Post.aspx?ThreadID=3950&PostID=13520). To make a long story short, in order to make my model work correctly I have to manually edit the generated Model.cs file to comment out / delete the DataMember attribute from one end of the relationship. If I don't, reading a master data table can result in the entire database being loaded along with it. This is a major PITA, and requires diligence on my part and in general, a lack of maintainability in the future. How do you even document that so the next app maintainer knows what to do? Or me in 5 years, even? I asked before, but got no response at the time -- can you please incorporate designer support for this? Maybe call it a one-way relationship or something, so both ends don't get the DataMemberAttribute decoration? Requiring the user (me) to manually edit generated code is really, really bad practice... Thanks, Dave |
|
|
Hi Dave, Yes we definitely intend to include new functionality into the designer to more precisely control the DataMember attributes in the manner you are looking for, I will certainly let you know once this has been included and is available in the nightlies.
Jeremy |
|
|
Thank you! You guys are awesome... |
|