Evengard

That actually did help, although I received a weird NullReferenceException somewhere deep in LinqToDb internals during enumeration of contents of a Grouping. Fortunately enough, that Grouping was easily converted into...

Still, this problem mostly occured due to the MappingSchemas being set up globally instead per context/DataConnection. Probably this conflict between PostgreSQL and MySQL mappings wouldn't occur, if they would be...

Sort of a follow-up on this grouping problem. It seems that this fix actually breaks something inside groups on left joins with DateTime parameters in the WHERE clauses. ``` Object...

It really seems that for some reason, the grouping aren't materialized on `FirstOrDefaultAsyncLinqToDB`/`ToArratAsyncLinqToDb`. And on iteration of the grouping it tries to materialize it, but fails...

Apparently, there's some kind of inherent incompatibility of DateTimes from Linq2Db (which apparently are all being processed as Kind.Unspecified) and Npgsql (with their new processing of DateTimes since 6.0). This...

@kamyker It works for you with the same converters as above?

Yeah, I guess this bug was introduced when Npgsql changed the DateTime processing.

I guess this falls under the "hierarchy per table" thing which isn't really supported, right?

Well, EF Core itself does create a "Discriminator" field in the database itself...

Ok, let me rephrase the question - is there a way to define a database-generated field with linq syntax with help of linq2db?