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

sql: multiple FK constraints on the same column are erroneously allowed in 19.1 #42486

Closed
thoszhang opened this issue Nov 14, 2019 · 1 comment
Assignees

Comments

@thoszhang
Copy link
Contributor

thoszhang commented Nov 14, 2019

In 19.1, and possibly earlier versions, we accidentally neglected the primary key when checking all indexes to ensure that no column is involved in more than one foreign key constraint (on the referencing side). There's no specific incorrect behavior expected from this, but it still leads to confusing results, as in #42400.

See #37590 (comment) for another example.

This was fixed incidentally by #37433 in 19.2, but we can backport a fix to 19.1.

@thoszhang
Copy link
Contributor Author

Closing - we're not going to "fix" this in past versions, see #42400 for more context

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant