{"push_id":650799738,"size":2,"distinct_size":1,"ref":"refs/heads/fix2074","head":"e22a909cb33ae0524e0316bd6c62649c82eb606b","before":"9a864cd955dca5e28a01ea4420586d863deb9173","commits":[{"sha":"283a8aa3b0325788c7552bd4bd137db73b006088","author":{"email":"26eddd122d65715c5a2ed9c3f23c8bb54ed13742@outlook.com","name":"Alex Forbes-Reed"},"message":"unwrapping nullable types on ValueGeneratorSelectors, updated tests to test for nullable guid's.","distinct":false,"url":"https://api.github.com/repos/aspnet/EntityFramework/commits/283a8aa3b0325788c7552bd4bd137db73b006088"},{"sha":"e22a909cb33ae0524e0316bd6c62649c82eb606b","author":{"email":"e63cca12db9015d6c29876c857990c1723c23c5c@microsoft.com","name":"Maurycy Markowski"},"message":"Fix to #2074 - allow users to opt-out from using null comparison expansion\n\nAdded UseRelationalNullComparisonsQueryAnnotation that can be used to annotate the query with information that it should not expand null comparisons.\n\nIf relationl null comparisons are required, we annotate the predicate with NonNullableExpression, so that null semantics expansion is skipped during sql gen (since we don't have access to query annotation at that point, the information must flow in the query itself).\nBecause of that we can only reduce the predicate in the query generation, after the second null semantics has been (potentially) applied. Before we it was possible to do it safely in CompositeRelationalExpressionTreeVisitor, but now the reducible information is needed is sql gen.\n\nAlso fix a minor bug around Annotations - if annotations were passed into the query via AnnotateQuery (FromSql, AsNoTracking, etc), we would not be using the name of lambda parameter as alias for the table, but rather use a first letter of entity type for that table. This was happening because Relinq created a subquery from the AnnotateQuery method call, that we later on optimize, but during the process we were not preserving the ItemName of the outer query. Since the AsNoTracking didn't have a lambda, Relinq couldn't figure out the proper ItemName and was using a generated name. Fix is to preserve the ItemName of the outer query and use it, instead of the inner query name, if the latter is generated (and former is not)\n\nCR: Andrew, Micah, Diego, Arthur.","distinct":true,"url":"https://api.github.com/repos/aspnet/EntityFramework/commits/e22a909cb33ae0524e0316bd6c62649c82eb606b"}]}