-
Notifications
You must be signed in to change notification settings - Fork 109
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
move unique constraint checking until after optimistic insertion #2037
Conversation
What's the deal with all the test failures? |
1eebec1
to
1d4d126
Compare
Seems one file ended up in the stash that shouldn't have. |
Can you bring in latest master to fix the "Internal Tests" job? |
1d4d126
to
57fd564
Compare
Yep, done. |
57fd564
to
f45b027
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
AFK and not gonna do a full review RN; will follow up in the morning. Just don't want to forget this.
d15faf7
to
459601f
Compare
459601f
to
46094e0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor nits, mostly comment-ey. Code looks good, and is correct AFAICT.
11391fe
to
c3f304a
Compare
Description of Changes
Move unique constraint checking until after the row has been inserted and roll back if there was a violation.
We need to do this to enable insertion via BSATN as we no longer will have a PV.
After insertion, we can instead project
RowRef
s to the index types.This should also facilitate moving indices out of tables.
Testing
Proptests are amended to reflect new order.