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
[WIP] Add primary keys to some tables for BDR. #1689
Conversation
Once the Greenwave patch is merged I'll rebase this one on top and give it a revision. |
Signed-off-by: Patrick Uiterwijk <puiterwijk@redhat.com>
I've rebased this PR on the Greenwave patch, but the migration fails to apply on the first step due to duplicates:
Thus, we are going to need to remove duplicates on these tables. After a quick glance at these uniqueness constraints, I think they do make logical sense to be unique since I think each relationship only makes sense to exist once in these through tables. Not all through table relationships make sense to be unique in general though. I.e., nothing says it's inherently "wrong" to put a relationship between two objects twice in a through table. I wonder how things like that should be modeled under BDR… |
Unfortunately I don't have time to finish this right now since it's more complex than it seemed it would be (due to the duplicate entries). I'm going to close the PR, but it's still linked in the issue so the patch isn't lost. |
fixes #1318
Signed-off-by: Patrick Uiterwijk puiterwijk@redhat.com
This patch was written by Patrick as noted above. I didn't have time to get it fully ready to merge (the migration needs a hash still), but I wanted to go ahead and post the PR since he sent it to me today. I'll clean it up soon and get it ready for review.