You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As part of EF Core 7 there are migrations tooling improvements, including allowing null for UseSqlServer. It is not clear to me if that change is only during design time or if it was relaxed in every case, but that would be a nice feature for the MySQL provider for getting rid of "dummy" connection strings that are there just to instanciate the DbContext in design time (something I have to do every time when developing a multi-tenant app that doesn't have a default connection, might also just be my lack of knowledge of alternative methods).
The text was updated successfully, but these errors were encountered:
victor-borges
changed the title
Feature request: Accept null connection string in UseMySql
Accept null connection string in UseMySql
Dec 12, 2022
As part of EF Core 7 there are migrations tooling improvements, including allowing null for UseSqlServer. It is not clear to me if that change is only during design time or if it was relaxed in every case, but that would be a nice feature for the MySQL provider for getting rid of "dummy" connection strings that are there just to instanciate the DbContext in design time (something I have to do every time when developing a multi-tenant app that doesn't have a default connection, might also just be my lack of knowledge of alternative methods).
The text was updated successfully, but these errors were encountered: