that's the cascade of p2 being added to the session upon being associated with the in-session items in p.children. So yes, cascade rules do add things to the session. setting cascade=None on Child.parent would prevent it, or alternatively you can turn off autoflush on the session for the span of the __init__ method by just setting the ".autoflush" attribute to False.
On Jan 29, 2009, at 5:55 AM, GustaV wrote: > > I quite sure I'm not using it... > > Look at that code that reproduce the "bug" > http://utilitybase.com/paste/11481 > The last line ("p2 = Parent(p)") leads to a load of the children, so > an autoflush. I have a failure with 0.5.2: > "sqlalchemy.exc.IntegrityError: (IntegrityError) parent.dumb may not > be NULL u'INSERT INTO parent (dumb) VALUES (?)' [None]" > which let me think the object was somehow added to the autoflush... > > I hope that will help to solve this. > > GustaV > > --~--~---------~--~----~------------~-------~--~----~ 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 sqlalchemy+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
