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

Model configuration: Don't throw when SqlServer ValueGenerationStrategy is configured on an incompatible property by a convention #7208

Closed
AndriySvyryd opened this issue Dec 8, 2016 · 1 comment
Labels
closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. type-bug
Milestone

Comments

@AndriySvyryd
Copy link
Member

No description provided.

@AndriySvyryd AndriySvyryd changed the title Don't throw when SqlServer ValueGenerationStrategy is configured on an incompatible property using a convention Don't throw when SqlServer ValueGenerationStrategy is configured on an incompatible property by a convention Dec 19, 2016
AndriySvyryd added a commit that referenced this issue Dec 22, 2016
AndriySvyryd added a commit that referenced this issue Dec 22, 2016
@divega divega added the type-bug label Jan 3, 2017
@divega divega added this to the 2.0.0 milestone Jan 3, 2017
@divega
Copy link
Contributor

divega commented Jan 3, 2017

Assigned PR to @ajcvickers so that you two can discuss whether we really need to do this.

AndriySvyryd added a commit that referenced this issue Jan 13, 2017
@AndriySvyryd AndriySvyryd removed their assignment Jan 13, 2017
@divega divega added the closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. label May 8, 2017
@ajcvickers ajcvickers changed the title Don't throw when SqlServer ValueGenerationStrategy is configured on an incompatible property by a convention Model configuration: Don't throw when SqlServer ValueGenerationStrategy is configured on an incompatible property by a convention May 9, 2017
@divega divega added closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. and removed closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. labels May 10, 2017
@ajcvickers ajcvickers modified the milestones: 2.0.0-preview1, 2.0.0 Oct 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. type-bug
Projects
None yet
Development

No branches or pull requests

3 participants