Maurycy Markowski

merged for 8.0.6 in https://github.com/dotnet/efcore/pull/33692, closing

I didn't get a chance to look into it yet. We have a huge backlog of work items at the moment, so response times are longer than usual. I will...

Currently JSON entities are internally mapped using owned types, which don't allow setting comment on them. Once we enable mapping JSON using complex types, this should light up "for free"....

MySql has to deal with a similar problem, you can try copying their solution: https://github.com/PomeloFoundation/Pomelo.EntityFrameworkCore.MySql/blob/main/src/EFCore.MySql/Query/Expressions/Internal/MySqlComplexFunctionArgumentExpression.cs With that approach, your SqlFunctionExpression would take first argument representing the date and the second...

There are several aspects to this issue. First thing is delimiting the path (when necessary), as @perfectphase suggested. Another thing is escaping non-standard characters. We use `Utf8JsonWriter` to build JSON...

looks this way @ajcvickers https://learn.microsoft.com/en-us/dotnet/standard/serialization/system-text-json/use-utf8jsonreader#use-valuetextequals-for-property-name-lookups ``` Don't use ValueSpan to do byte-by-byte comparisons by calling SequenceEqual for property name lookups. Call ValueTextEquals instead, because that method unescapes any characters that...

Alternative way we can go with: ``` utf8Reader.ValueTextEquals( MemoryExtensions.AsSpan( (ReadOnlySpan)Encoding.UTF8.GetBytes(propertyName))) ```

additional info from EF perspective: when OData is out of the picture (i.e. using `Include` operation in EF), there will be no duplication: ```cs ctx.Incidents.Include(x => x.Alerts).Select(incident => new Incident()...

sadly there is no good workaround - Count is effectively pruning the projection, so we can't do any tricks to circumvent the issue. Either entity must have a key, or...

reopen for potential servicing