On Feb 10, 11:48 am, Michael Bayer [EMAIL PROTECTED] wrote:
del p.children[3]
basically cascade has nothing to say about this operation when applied to
transient instances. the history tracking will not see the item as ever
being part of the children collection since you added it then
The following code raises a FlushError because the child object named
Cheshire is an orphan and the delete-orphan cascade rule is in effect.
It seems to me that an orphan which has no database identity should be
detached from its session, just as it was attached when appended to a
parent's list
Forgot to say I'm using SA 0.3.4.
On Feb 9, 5:05 pm, SteveTether [EMAIL PROTECTED] wrote:
The following code raises a FlushError because the child object named
Cheshire is an orphan and the delete-orphan cascade rule is in effect.
It seems to me that an orphan which has no database identity
