On Aug 12, 2012, at 7:15 PM, Michael Bayer wrote: > > the constructor issue someone mentioned is the source of the issue here. > However there is also an odd leapfrog between Author and Story occurring > (since they both have backrefs of the same name "comments") that the ORM > ideally would be able to detect before running forever, will look into that.
that's fixed in 0.8 and 0.7.9, error is now: ValueError: Object <Story at 0x10151d490> not associated with attribute of type Comment.author while this error message looks like a generic "attribute set mismatch" message, it is only generated when this particular situation occurs in a backref, as this particular condition can be detected in a performant way at that stage and also causes a catastrophic failure otherwise. setting the wrong object on an attribute in general will usually fail during the session cascade or flush stage. -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected]. 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.
