fix partial delete multi value index unexpected behavior #3677
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
…n composite key, when rid wasn't specified.
expected behavior, to remove all values under specified (partial/full) key
-remarks: all test passed after fix
lvca
added a commit
that referenced
this pull request
Mar 2, 2015
fix partial delete multi value index unexpected behavior
|
Thanks! |
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.
manual index command, DELETE FROM index: WHERE key =
was failing on composite key, when rid wasn't specified.
expected behavior, to remove all values under specified (partial/full) key
Use case:
CREATE INDEX index:test notunique string,string
INSERT INTO index:test (key,rid) values (['test','me'],#1:1)
INSERT INTO index:test (key,rid) values (['test','me'],#1:2)
DELETE FROM index:test where key = ['test']
SELECT FROM index:test
expected return 1 row
actual return 2 row
related to #2741