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
If I scaffold Sql Server Database using 'dotnet ef dbcontext scaffold', it does not handle properly nvarchar(4000) columns. They are generated as HasType("nvarchar") without length specification. This cause exception during model validation phase.
Further technical details
EF Core version: 2.0 RTM
Database Provider: Microsoft.EntityFrameworkCore.SqlServer
Operating system: Win 10
IDE: Visual Studio 2017.3
The text was updated successfully, but these errors were encountered:
Hi @SergeyBarskiy. We are gathering information on the use of EF Core pre-release builds. You reported this issue shortly after the release of 2.0.0 RTM. It would be really helpful if you could let us know:
Did you consider testing your code against the pre-release builds?
Was there anything blocking you from using pre-release builds?
What do you think could make it easier for you to use pre-release builds in the future?
Thanks in advance for any feedback. Hopefully this will help us to increase the value of pre-release builds going forward.
@ajcvickers
Hey, Arthur.
No, we have not tried against pre-release builds.
No, nothing in particular when it comes to just testing
I do not think anything else needs to be done.
We primarily stopped the investigation because of the other issue I found - startup times on a large context (1000) tables was taking 2 minutes (#9347) , which is not really acceptable to our company at this point.
If I scaffold Sql Server Database using 'dotnet ef dbcontext scaffold', it does not handle properly nvarchar(4000) columns. They are generated as HasType("nvarchar") without length specification. This cause exception during model validation phase.
Further technical details
EF Core version: 2.0 RTM
Database Provider: Microsoft.EntityFrameworkCore.SqlServer
Operating system: Win 10
IDE: Visual Studio 2017.3
The text was updated successfully, but these errors were encountered: