Version: DataObjects.Net v4.3.0 (build 5605) for .NET 4.0 DB Engine: MS SQL Server 2008

Have this model:

[Serializable]
[HierarchyRoot]
[TableMapping("Persons")]
public class Person : Entity
{
    [Field, Key]
    [TableMapping("ID")]
    public int Id { get; private set; }

    [Field(Length = 32)]
    public string Name { get; set; }

    [Field(Length = 64)]
    public string Surname { get; set; }

    [Field(Length = int.MaxValue)]
    public string Hobbies { get; set; }

    [Field]
    public EntitySet<Car> Cars { get; private set; }
}

[Serializable]
[HierarchyRoot]
[TableMapping("Cars")]
public class Car : Entity
{
    [Field, Key]
    [TableMapping("ID")]
    public int Id { get; private set; }

    [Field(Length = 128)]
    public string Name { get; set; }

    [Field(Length = int.MaxValue)]
    public string Description { get; set; }

    [Field]
    [Association(PairTo = "Cars", OnOwnerRemove = OnRemoveAction.Deny, OnTargetRemove = OnRemoveAction.Cascade)]
    public Person Owner { get; set; }
}

In entity class Car i have defined association like this:

[Association(PairTo = "Cars", OnOwnerRemove = OnRemoveAction.Deny, OnTargetRemove = OnRemoveAction.Cascade)]

As i read manual then setting OnTargetRemove = OnRemoveAction.Cascade means that when person is removed than all associated cars with this person is also removed, right?

Removing person from C# code also removed associated cars, which is OK. But when i look at generated SQL foreign key in table "Cars" then this foreign key has set action "On Delete" to value "NO ACTION" which is wrong, there should be value "Cascade" like defined in code in association attribute, isnt?

Updated at 28.07.2010 18:13:48

These actions are handled purely on BLL level (i.e. by DO), so OnXxxRemove value don't affect on foreign key constraints.

I thought that, but is this right? Is there any reason why it is not also on DB foreign key?

This thread was imported from our support forum. The original discussion may contain more detailed answer.