Smit Patel

@fgheysels - That is valid use-case. At present, when they are mapped in same table, they uses same column for PK. In current implementation there is no way to figure...

Also consider API to mark the SQL as non-composable so we would run it as-is.

> Looks like ExpressionEqualityComparer needs to recognize and treat arrays in a special way.. Elaborate. There is no array in compare in expression tree. If you have run the repro,...

We shouldn't be doing deep equality comparison in ExpressionEqualityComparer at least for this scenario since it is the entry point for query cache. A deep comparison at this point for...

```C# var array = new [] { 1, 2, 3 }; var exp = dbContext.TestModels .Where(x => array.Contains(x.Test)) .Expression; ```

That could be good compromise.

Can we also get tests which converts from actual string values. Also some negative tests where the string is not exactly parse-able and we verify database behavior.

Just to answer how to do it, add a custom implementation `IQueryTranslationPostprocessor` deriving from `RelationalQueryTranslationPostprocessor` and replace `ShapedQueryExpression.QueryExpression` which would be a `SelectExpression` with a different `SelectExpression` to generate same...

#20758 is different issue from this one. Subquery join vs table join is only equivalent without side effects when subquery doesn't have any additional operators. If you look at the...

Requires actual query tests. Why don't we not allow projection member binding for JsonEntityExpression?