Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

timgraham
Copy link
Member

@timgraham timgraham commented May 29, 2017

@timgraham
Copy link
Member Author

@charettes @schinckel -- any advice about things to try for a solution?

@charettes
Copy link
Member

charettes commented May 29, 2017

@timgraham it looks like it's caused by the call to unification_cast_sql in Subquery.as_sql(), what happens if you completely remove it?

@timgraham timgraham changed the title [WIP] Fixed #28199 -- Fixed Subquery __in generating unnecessary/invalid CAST. Fixed #28199 -- Fixed Subquery generating unnecessary/invalid CAST. May 29, 2017
Copy link
Member

@charettes charettes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@timgraham I'm pretty sure the inclusion of this code was a copy-paste leftover of the Case.as_sql() occurrence as it doesn't make much sense to be used here. Thanks for the tests!

@schinckel
Copy link
Contributor

Yeah, I don't recall whether there was a reason that was there. Probably more that I don't know exactly what it's supposed to do.

No failing tests elsewhere means it's either not needed, or needed for something that's not tested, I guess.

@timgraham timgraham merged commit f044955 into django:master May 30, 2017
@timgraham timgraham deleted the 28199 branch May 30, 2017 10:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants