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.
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
Allow disable transaction for select populates #1067
Allow disable transaction for select populates #1067
Changes from all commits
183b95f
e3f1f10
9f6f9a3
d75e875
9ac0935
712f945
6c24b34
03b87ce
fedfe96
d8a1c0b
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
I think it could be made simpler for the user to clean up the mismatched hash insert by either:
insert
if there's a hash (enforces integrity, requires more edits to the code)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.
Only using the hash makes it tough to determine where the mismatch occurred. I made a commit to delete all the keys and ask the user to start over. It's not ideal, but, from the code I've seen, folks primarily run one key at a time. It seems like an unlikely case that there would be a mismatch - and that it'll have a serious impact in the timeline between now and a new DJ feature we can use
Would you rather I run a table-wise comparison across the two
RestrGraph
objects to nail down where the mismatch occurred?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.
I think the overly cautious solution of delete them all is fine for now. As you said, it's unlikely that it would occur, and ensuring consistency is a valid priority. User's shouldn't notice it, and if they do we would need to be going back into the code to figure out why anyways