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

Clarify how primary keys interact with value generation #1907

Merged
merged 1 commit into from
Nov 10, 2019

Conversation

AndriySvyryd
Copy link
Member

Fixes #1046

@@ -48,7 +49,7 @@ Like `value generated on add`, if you specify a value for the property on a newl

## Conventions

By convention, non-composite primary keys of type short, int, long, or Guid will be setup to have values generated on add. All other properties will be setup with no value generation.
By default, non-composite primary keys of type short, int, long, or Guid will be setup to have values generated on add. All other properties will be setup with no value generation.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it still true that you don't get value generation if the property is part of a composite? I vaguely remember that we (possibly unintentionally) changed this.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, we changed this back for non-owned types. And I don't think we need to talk about owned types here.

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.

Primary key types
2 participants