Description David Minsky 2011-04-12 16:03:08 EDT

Problem description:

- Two descriptors ("A" & "B") reference a third child descriptor ("C")(privately owned), with cascade locking (& version locking)
- Child descriptor ("C") references another descriptor ("D") (privately owned)
- Depending on the order of descriptor initialization, descriptor D can contain 2 duplicate cascade locking policy instances, because both A and B reference its parent C
- This increases SQL traffic to the DB, as duplicate lookups are performed when changes are detected for D
- D should only have one cascade locking policy to minimize SQL calls