fixes #104: fixes duplicate fields issue and adds support for compound primary keys#118
Open
tomjoro wants to merge 1 commit intojhartwell:masterfrom
Open
fixes #104: fixes duplicate fields issue and adds support for compound primary keys#118tomjoro wants to merge 1 commit intojhartwell:masterfrom
tomjoro wants to merge 1 commit intojhartwell:masterfrom
Conversation
…ry key and other index
tomjoro
changed the title
tomjoro
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
fixes #104
Composite primary keys are supported by generated multiple true primary_key fields according to ecto specifications.
I also changed code so it only emits primary_key when it is true. This makes it much more readable.
This fix only affects Postgres.