On 5/23/15 9:01 PM, Mike Bayer wrote:
The best I can do is that there's a patch that can make this work but I definitely cannot commit it in 1.0; the eager loading mechanics are extremely sensitive and easily messed up by even the most subtle change, and I'd have to find time to think and test this very deeply and at best it would be for 1.1. That issue is at https://bitbucket.org/zzzeek/sqlalchemy/issue/3431/object-eager-loaded-via-two-separate-paths.
I've just done some of that thinking and I'm optimistic I can have this patch added in 1.1. It should be the correct approach based on everything else I'm looking at. But 1.1 is not due for a release for many months at the earliest, unfortunately.
-- 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/d/optout.
