Feel free to add a trac ticket to that, it is a bug and will require some re-think to work out.
On Jan 17, 2014, at 2:41 PM, Navid Sheikhol Eslami <[email protected]> wrote: > I believe I may have hit a bug in the way SQLAlchemy handles multiple table > updates. I have written a test unit to reproduce the problem: > > http://pastebin.com/4veNE4A8 > > Apparently if trying to update two columns with the same name, only one > column is actually updated while the other one is silently ignored (does not > even show up in the UPDATE query). > > As shown in the test unit, I'd expect the Parent row to have its "name" > column updated to "newparentname" but that's not the case. > > -- Navid > > -- > 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.
signature.asc
Description: Message signed with OpenPGP using GPGMail
