On Jul 25, 2013, at 5:21 PM, Michael Bayer <[email protected]> wrote:
> > collection isn't present and such and there are still lots of endless loop > cases that come up (I just tried in tests and many fail if I remove this > check). The recursion checks in this area are fairly aggressive as there > are a lot of edge cases that can occur, sometimes due to user error, where we > can't efficiently determine at what point we need to stop backreffing. I > have a little bit of time at the moment so I can look to see if in the > current codebase there might be some refinement that can be easily made. this issue is now resolved, and SQLAlchemy 0.9 will feature an enhanced system within the attribute event system which it uses to detect at what point it needs to stop propagating a backref event. The backref handlers themselves have taken over the job of controlling at what point the event propagation should stop. A full description of the change and the ramifications it might have for custom event handling situations (which is not your case here) is up in the migration guide at http://docs.sqlalchemy.org/en/latest/changelog/migration_09.html#backref-handlers-can-now-propagate-more-than-one-level-deep . -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/groups/opt_out.
