Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Scaffolding of Sql Server DbContext does not handle properly nvarchar(4000) columns #9438

Closed
SergeyBarskiy opened this issue Aug 17, 2017 · 4 comments

Comments

@SergeyBarskiy
Copy link

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

@smitpatel
Copy link
Contributor

duplicate of #9188

@ajcvickers
Copy link
Contributor

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.

@SergeyBarskiy
Copy link
Author

@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.

@ajcvickers
Copy link
Contributor

@SergeyBarskiy Thanks for the feedback; much appreciated.

@ajcvickers ajcvickers reopened this Oct 16, 2022
@ajcvickers ajcvickers closed this as not planned Won't fix, can't repro, duplicate, stale Oct 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants