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

Throw in model validation for unqualified types like "nvarchar" and "varbinary" #4500

Merged
merged 1 commit into from
Feb 9, 2016

Conversation

ajcvickers
Copy link
Member

If the app really wants a data type like this with a length of one, then it should use, for example, "nvarchar(1)". This stops apps from putting, for example, nvarchar and then setting a max length of 16 in the API and expecting this to be transformed into the type nvarchar(16).

Also, some cleanup in the type mapper and model validator classes.

@rowanmiller
Copy link
Contributor

✅ Exception message looks good

@AndriySvyryd
Copy link
Member

:shipit:

…varbinary"

If the app really wants a data type like this with a length of one, then it should use, for example,  "nvarchar(1)". This stops apps from putting, for example, nvarchar and then setting a max length of 16 in the API and expecting this to be transformed into the type nvarchar(16).

Also, some cleanup in the type mapper and model validator classes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants