One-Way One-To-One Associations

I'm evaluating Lightspeed against other data access alternatives - NHibernate, EF, Micro ORMs, spring data, etc...

I'm having issues with a couple things:

1. I have a Person and an Address. I'd like to enforce containment so that someone can't traverse the object graph up to person from address. I can't seem to do this in the designer. I can hand edit the generated code obviously.

2. Cascade delete of the same relationship - I can't seem to cascade delete Address from Person. I've tried using the NoReverseAssociationAttribute on the entity holder, etc and I can't seem to get it to work.

Calling this does not work:

.Remove(person);  
.SaveChanges(true); 

This does (for obvious reasons):

var addressId = 0;
if (entity.CurrentAddress != null)
    addressId = entity.CurrentAddress.Id;

_uow.Remove(entity);

if (addressId > 0)
    _uow.Remove(new Query(typeof(Address)) { Identifier = addressId });

_uow.SaveChanges(true);

I can also do something similar:

 if (entity.CurrentAddress != null)
 {
     _uow.Remove(entity.CurrentAddress);
 }

 _uow.Remove(entity);

 _uow.SaveChanges(true);

Any thoughts?

Thanks.

Jon

The designer doesnt support the notion of one way associations as all associations in LightSpeed are expected to be bi-directional. As you have deducted you can represent these manually as part of partial class definition but if you do so then you will want to avoid using our EntityHolder/EntityCollection types as these will expect a bi-directional relationship to be present.

For the cascade delete, because you have the relationship as nullable make sure you set the IsDependant attribute on the relationship. Also which side of the relationship do you currently have the FK defined on? e.g. do you have a Person.AddressId or do you have an Address.PersonId?

Jeremy

Jeremy

Thanks for the feedback. I have the standard normal form of a fk_currentaddress field in the table for people.

Jon