{"push_id":648901302,"size":1,"distinct_size":0,"ref":"refs/heads/dev","head":"50def6473bd450d90129248e45dc0ea5ef86152c","before":"65fcced33c3e373e04636f661d9abec59ea93437","commits":[{"sha":"50def6473bd450d90129248e45dc0ea5ef86152c","author":{"email":"e63cca12db9015d6c29876c857990c1723c23c5c@microsoft.com","name":"Maurycy Markowski"},"message":"Fix to #2027 - improve the way we build IsNull expressions for null semantics\n\nProblem was that in null semantics, when we test whether expression is null or not, we assumed incorrectly that the expression is null if either of it's parameters is null.\nThis works for most cases (e.g. functions), but not for all.\nExapmles are COALESCE and CASE-WHEN-THEN-ELSE.\n\nFix is to refactor the visitor that is used for that purpose, before it was just extracting nullable expressions, now it builds the entire IsNullExpression tree.\n\nAlso fixed some minor issues with case expression - we were assuming it would always produce expression of type bool, but it's no longer the case.\nOn top of that, fixed SQL gen formatting for case expressions, so that it's more readable for more complex cases.\n\nCR: Andrew","distinct":false,"url":"https://api.github.com/repos/aspnet/EntityFramework/commits/50def6473bd450d90129248e45dc0ea5ef86152c"}]}