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.

Sign up for GitHub

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

Jump to bottom

Key.ReferencingForeignKeys can have different orderings #6295

Closed
ajcvickers opened this issue Aug 11, 2016 · 0 comments
Closed

Key.ReferencingForeignKeys can have different orderings #6295

ajcvickers opened this issue Aug 11, 2016 · 0 comments
Labels
closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. type-bug
Milestone
1.1.0

Comments

@ajcvickers
Copy link
Contributor

Depending on how the model is built, Key.ReferencingForeignKeys can get FKs added in different orders. These models should be functionally equivalent, but could cause issues with name-generation etc. This can in turn cause issues with model diffing, etc. Therefore we might want to make this collection have a fixed order. We should also look for other similar collections and do likewise.
@divega divega added this to the 1.1.0 milestone Aug 12, 2016
ajcvickers added a commit that referenced this issue Oct 12, 2016
@ajcvickers
Explicit ordering for Key.ReferencingForeignKeys
debe220 
And also some other metadata collections.

Issue #6295
@ajcvickers ajcvickers mentioned this issue Oct 12, 2016
Merged
ajcvickers added a commit that referenced this issue Oct 12, 2016
@ajcvickers
Explicit ordering for Key.ReferencingForeignKeys
afecde8 
And also some other metadata collections.

Issue #6295
ajcvickers added a commit that referenced this issue Oct 12, 2016
@ajcvickers
Explicit ordering for Key.ReferencingForeignKeys
cbcef85 
And also some other metadata collections.

Issue #6295
@ajcvickers ajcvickers added the closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. label Oct 12, 2016
@ajcvickers ajcvickers modified the milestones: 1.1.0-preview1, 1.1.0 Oct 15, 2022
@ajcvickers ajcvickers removed their assignment Sep 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
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
Milestone
1.1.0
Development

No branches or pull requests
3 participants
@divega @ajcvickers @AndriySvyryd