Glen

@AlexeyRaga @michaelstaib Was this resolved by #5973?

Thanks for the summary, though I'm asking more specifically about this particular issue – has the error in the OP been resolved? If so, I'll go ahead and close this...

@PascalSenn I spent some time looking into this, and: - The default collation for MySQL and MS SQL Server is case-insensitive, and the default for PostgreSQL and SQLite is case-sensitive....

Closing for the above reasons.

@PascalSenn This PR is now over 2 years old. Do you intend to move forward with it at some point, or should it be closed?

@michaelstaib Would you consider reopening this to look at terser solutions as proposed by the OP? Defining this in the `SortInputType` seems like a cleaner option, and avoids having to...

We decided on a different direction, automatically applying a sort by ID to ensure deterministic ordering. ```cs /// /// Extends the to apply an additional order by ID, to ensure...

Closing, as this appears to have been resolved.

@lauxjpn Will it be possible to configure options at the property level? For example: ```cs builder .Property(f => f.Metadata) .HasColumnType("json") .JsonSerializerOptions((options) => ...); ```

I wonder if all the complexity of creating a hash from the builder configuration, ignoring certain properties, etc. is necessary? Would it not work to simply have an API similar...