Kevin,
what kind of problems? During the deletion or the subsequent commit?
If that's on commit, the ordering is determined using dependency
graph analysis with AshwoodEntitySorter (i.e. not dependent on the
order of delete rules processing). It works well except for circular
relationships.
Andrus
On Oct 22, 2007, at 11:35 PM, Kevin Menard wrote:
> Howdy.
>
> I've just run into an issue with some of my cascading delete
> rules. Trying
> to reproduce the problem has been difficult because the ordering
> seems to be
> non-deterministic. Looking at the source, it looks like the delete
> operations are stored in a Map that has no internal ordering of the
> keyset.
>
> DataContextDeleteAction#deleteNew() and
> DataContextDeleteAction#deletePersistent() also process the delete
> rules in
> a different order. As it turns out, it may not matter much.
>
> Is this assessment accurate? If so, we probably should always process
> delete rules first, then the current node, using a DFS to handle the
> creation of the delete queries. If the assessment is not accurate,
> any help
> in understanding what may cause spurious issues with cascading
> deletes would
> be appreciated.
>
> --
> Thanks,
> Kevin
>
>
This archive was generated by hypermail 2.0.0 : Mon Oct 22 2007 - 16:56:49 EDT