Diego Vega

@smitpatel let’s bring this to a design meeting. I would be ok with the overload with StringComparison started to throw in the default implementation in absence of client eval, but...

@smitpatel Besides, I believe many databases will default to case insensitive comparisons anyway, so what is harder to achieve is a case sensitive one.

@BalassaMarton if you control the database schema it is preferable to specify a column collation that will compare string according to your preference. If you have a case insensitive collation...

Un-combining.

This need came up while prototyping the solutions for https://github.com/aspnet/Identity/issues/457. In that particular scenario a few new columns need to be added to the database as part of the upgrade,...

Noticed this issue has the pri0 but hasn't been assigned. Assigning to @bricelam since he owns our migrations story.

Also, note that the proposal described in a previous comment should be much easier to implement if the IModel that is the output of the reverse engineering pipeline used the...

@EdwardL75 I remember @HaoK did an exercise to identify additional steps necessary to upgrade from a database that doesn't have the normalized columns (i.e. from an ASP.NET Identity 2.0 database...

@EdwardL75 Understood. I think the approach that @HaoK is pointing to does that, but if I remember correctly, it had some disadvantages, e.g. lookups will be resolved in memory. Anyway,...

@bricelam to provide workaround. @divega to follow up about how this works on deployment.