This question is locked. New answers and comments are not allowed.
Hello,
I am noticing that immediately after I create a new object and call my contexts .add sub. A select Query is automatically issued by the context for those objects that have relationships defined. I assume this is to populate all of those relationships correctly. However it can lead to several call backs that are not needed and costly over a WAN environment. Is there a specific way for me to insert objects without this from happening?
Brent
I am noticing that immediately after I create a new object and call my contexts .add sub. A select Query is automatically issued by the context for those objects that have relationships defined. I assume this is to populate all of those relationships correctly. However it can lead to several call backs that are not needed and costly over a WAN environment. Is there a specific way for me to insert objects without this from happening?
Brent
1 Answer, 1 is accepted
0
I think this could come from the handling of synchronized or managed fields, where we try to check if row exists in the database.
Would it be possible to send us your .rlinq file so that we can figure out this a bit more? If this comes from shared fields, then this might be an issue coming from a missing/wrong null indicator. If this is coming from managed collections, the issue might be a different one.
Kind regards,
Thomas
the Telerik team
Would it be possible to send us your .rlinq file so that we can figure out this a bit more? If this comes from shared fields, then this might be an issue coming from a missing/wrong null indicator. If this is coming from managed collections, the issue might be a different one.
Kind regards,
Thomas
the Telerik team
Telerik OpenAccess ORM Meets ASP.NET Web API. Read more.