Consider use of EF collations

[josephdecock]

Collation issues with EF have caused bugs in the past, and we work around that by performing a second case sensitive check in memory in our C# code.

EF core 5.0 added support for collations, which might improve this situation:

We can declare in our entity mappings that we need case sensitive collation:

modelBuilder.Entity<Customer>().Property(c => c.Name)
    .UseCollation("SQL_Latin1_General_CP1_CI_AS");

And we can specify a collation in a query:

var customers = context.Customers
    .Where(c => EF.Functions.Collate(c.Name, "SQL_Latin1_General_CP1_CS_AS") == "John")
    .ToList();

Open questions:

• Level of support for these features in various EF providers
• Can we set collation where we need it without breaking localizations?

[brockallen]

First thought -- should this be done in the customer's setup of the DB (globally)?