Smit Patel
Smit Patel
This could be cause for https://github.com/dotnet/efcore/pull/29157 too.
Same happens for owned collections which are always mapped to different table.
Also see #14179 which is about same type but different facets (albeit in slightly different form)
https://github.com/dotnet/efcore/commit/3ebfde7e51aa08692ed1278232e3f1d4beb779be
> new SqlFragmentExpression($"INTERVAL '{amountToAdd} {datePart}'"); Interpolated strings are culture specific. EF Core codebase specifically avoids interpolated strings unless combining strings due to this. I believe right thing to do here...
a slightly related thing, the actual character in the source code file may also matter depending on the encoding of the file it is difficult to figure out the difference.
I was going along the idea that if the file has bad character and server was also in same Norwegian culture then it would not treat it as bad character....
This will require changing `IsValidSelectExpressionForExecuteUpdate` method. - By default relational converts APPLY to JOIN if there are no outer references (or they can be lifted in join predicate), so APPLY...
Pending task here is to update fwlink to point to right location after docs are published. cc: @ajcvickers