> > > do your setProp() operation, then do this: > > (added, unchanged, deleted) = MyClass.props.get_history(myobject) > > to see whats actually in there. it should just be a collection of > "added" objects (and also, the correct objects). >
Yep, so far so good. Two Prop items in 'added' > > Then, use echo_uow=True on your session to see the flush plan. > everything in the flush plan should also be in an "added" collection > somewhere. also look inside of session.new, see if all the correct > stuff is in there too. session.new contents looks ok, with both Prop items and some other objects The UOW is large and complex (attached, the "Prop" items are named "Invoiceattr"), but I do see the Prop items in there, two of them. and...... same (database) error on flush > Objects which get removed from the collection due to your operation > should be raising an "orphan" error right now, since theyre in the > session but have no parent....seems like thats what your FK error is > but its unusual that the orphan detection wouldn't be working. > > OK, I get the basic idea; expunge isn't automatic. Let me rework the setProp to get things running again here, and then I'll pick up the discussion about that. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
r
Description: Binary data
