One-sided association and IsManaged

[Petr]

Is there a way have managed one-sided association?  Let's take this model for example (adding IsManaged() at the end). I'd like to be able to issue

var vendor = new Vendor { Name = "Vnd" };
vendor.VendorContacts.Add( new VendorContact { ContactType = "Type" });
model.Add(vendor);
model.Save();

 

 Sadly when I try to run this I get null exception and I have to save the contact first

var vendor = new Vendor { Name = "Vnd" };
var contact = new VendorContact { ContactType = "Type" };

model.Add(contact);
model.Save();

vendor.VendorContacts.Add( contact );

model.Add(vendor);
model.Save();

[Boris Georgiev]

Hello Petr,

The purpose of setting the IsManaged flag of the association to true is to let Telerik Data Access to synchronize both ends of the association. The first benefit of this is that the Foreign Key column/property will be populated automatically. The second benefit is that the child object will be added in the context because it will be persisted when both ends of the association are synchronized. When one end of the association is missing, there will be no effect of managing the association, because the two ends of the association cannot be synchronized and the second object cannot be persisted. This is why you are receiving the null exception.

I hope that helps.

Regards,
Boris Georgiev
Telerik

 

[Petr]

Hey Boris,

 so I can take that as

vendor.VendorContacts.Add( new VendorContact {Name = "Name"} );

model.Add(vendor);
model.Save();

cannot be achieved for a one sided associations. Would that be right?

Thanks~

[Boris Georgiev]

Hello Petr,

Yes, that is right. This behavior cannot be achieved for one sided association. You should have two sided association to get the benefits of using the IsManaged behavior.

If any other questions arise, do not hesitate to contact us again.

Regards,
Boris Georgiev
Telerik