On Monday 20 April 2015 13:24:49 Michael Bayer wrote:
>> On Apr 20, 2015, at 12:56 PM, Guido Winkelmann <guido@ambient-
entertainment.de> wrote:
>>> On Monday 20 April 2015 11:23:06 Mike Bayer wrote:
>>
>>> On 4/20/15 8:09 AM, Guido Winkelmann wrote:
>>>> On MySQL/PostgreSQL, this line fails:
>>>>
>>>> Apparently, sqlalchemy will use "symbol('NEVER_SET')" where the id of
>>>> the model used for filtering should be.
>>>
>>> this is a known regression and is fixed in 1.0.1:
>>> http://docs.sqlalchemy.org/en/latest/changelog/changelog_10.html#change-1.
>>> 0.1
>>>
>>>
>>> if you can confirm with current master that this is fixed I can release
>>> today or tomorrow as this particular regression is fairly severe.
>>
>> I just tested, the problem is still present in the current master
>> (bd61e7a3287079cf742f4df698bfe3628c090522 from github).
>
>Oh, read your text, while you haven't provided a code sample it sounds like
>you are possibly saying filter(Foo.relationship == some_transient_object)
>and expecting that all the None values come out. Yes? That is just the
>kind of example of "just happened to work" I'm talking about. Can you
>confirm this is what you are doing please ?
Yes, basically.
>Hopefully can find a fix for
>that. There is an entry detailing the behavioral change here but these
>effects were unanticipated (hence there were five betas, to little avail).
Guido W.
--
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 sqlalchemy+unsubscr...@googlegroups.com.
To post to this group, send email to sqlalchemy@googlegroups.com.
Visit this group at http://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/d/optout.
