Smit Patel comments

Results 190 comments of


                                            Smit Patel

trafficstars

Result of left joining a nullable nominal type should be null (i.e. no instance) and not an instance with all null property values

Note: This gave incorrect result in 3.1.x by initialize post with default values rather than returning null (the result of DefaultIfEmpty). With #20633 fixed, it now throws error. Right fix...

Result of left joining a nullable nominal type should be null (i.e. no instance) and not an instance with all null property values

Issues faced: When generating left join we need to add additional null check in selector so that we can generate correct default type if sequence is empty and not try...

Result of left joining a nullable nominal type should be null (i.e. no instance) and not an instance with all null property values

Work-around to original issue ``` var query = from blog in db.Blogs join post in dbPosts on blog.BlogId equals post.BlogId into posts from xpost in posts.DefaultIfEmpty() select new Blog {...

Result of left joining a nullable nominal type should be null (i.e. no instance) and not an instance with all null property values

@skclusive - Your query was giving incorrect results in 3.1, The bug fix for #20633 stopped generating incorrect results. In your case it throws exception because the query translation couldn't...

Result of left joining a nullable nominal type should be null (i.e. no instance) and not an instance with all null property values

@hhhuut - There is no one answer to the question. Essentially, when you do a left join, right side can have null values so accessing any property over that will...

Result of left joining a nullable nominal type should be null (i.e. no instance) and not an instance with all null property values

@StrangeWill - This is what will happen in EF Core 6.0 - If the selector does conditional expression before construction of anonymous type, then we will not create instance of...

Result of left joining a nullable nominal type should be null (i.e. no instance) and not an instance with all null property values

Related #19095

Smit Patel

Result of left joining a nullable nominal type should be null (i.e. no instance) and not an instance with all null property values

Result of left joining a nullable nominal type should be null (i.e. no instance) and not an instance with all null property values

Result of left joining a nullable nominal type should be null (i.e. no instance) and not an instance with all null property values

Result of left joining a nullable nominal type should be null (i.e. no instance) and not an instance with all null property values

Result of left joining a nullable nominal type should be null (i.e. no instance) and not an instance with all null property values

Result of left joining a nullable nominal type should be null (i.e. no instance) and not an instance with all null property values

Result of left joining a nullable nominal type should be null (i.e. no instance) and not an instance with all null property values

Bump xunit to 2.9.0

Bump xunit to 2.9.0

Allow forcing a constant in query filters