Ticket #116 (new defect)
Nested Iterators are not saved when parent.save() is called
| Reported by: | kend | Owned by: | dhughes |
|---|---|---|---|
| Type: | defect | Priority: | high |
| Milestone: | 1.0 Release | Component: | Reactor - Iterator |
| Version: | Severity: | major | |
| Keywords: | isDirty spam | Cc: |
Description
Given a Parent object with a hasMany relationship to n Children objects, each of which having a hasMany relationship with n SubChildren objects, modifications to the SubChildren (including adding or removing items from the SubChildrenIterator) does not set the isDirty property of the Children object, which results in those changes not being saved when Parent.save() is called. This seems to be the case for any level of nesting beyond one (Parent->Child.)
Change History
Note: See
TracTickets for help on using
tickets.

