Re: [sqlalchemy] Re: Unnecessary SELECTS for association object instances via composite key?

2016-09-02 Thread Mike Bayer
thanks for this test. this is issue https://bitbucket.org/zzzeek/sqlalchemy/issues/3788/simple-many-to-one-comparison-is-sensitive and the fix is going through targeted at 1.1 for now. On 09/02/2016 12:39 AM, YKdvd wrote: I think I may have found the issue. If I modify your example so that

[sqlalchemy] Re: Unnecessary SELECTS for association object instances via composite key?

2016-09-01 Thread YKdvd
I think I may have found the issue. If I modify your example so that "C.k1" is a declared_attr, the assertion on the second C instance loads the (100,1000) record from table "ab" again. I originally had my "k1" in a mixin, but it looks like the mixin isn't involved, and it is purely the

[sqlalchemy] Re: Unnecessary SELECTS for association object instances via composite key?

2016-08-28 Thread YKdvd
I'll see if I can add in the equivalent of any of the weirdness from the left/right classes or whatever from my setup to break this example and find out where I've messed up... :) There's a couple of oddities from one of them that might be possibilities, its been a couple of years or more since