[3Hl7fTsQ] Dev fix misleading name column #675
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gem-neo4j
force-pushed
the
dev_fix_misleading_name_column
branch
from
b7097c9 to
32659a5
Compare
gem-neo4j
changed the title
gem-neo4j
force-pushed
the
dev_fix_misleading_name_column
branch
from
32659a5 to
5db4bb4
Compare
gem-neo4j
force-pushed
the
dev_fix_misleading_name_column
branch
from
5db4bb4 to
2b3d99b
Compare
|
@loveleif in order to fix a failing test I had to make quite a few changes, when you have time can you review the second commit? :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The name column was different between these 2 equivalent procedures, and wasn't even actually giving the name of the constraint/index. So this makes it more consistent with SHOW CONSTRAINTS/INDEXES