Test literal equality handling on insert/delete #60
Conversation
This file contains hidden or 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
When `:literal_equality` is supported, ensure that RDF term-equality is preserved on write operations.
no-reply
force-pushed
the
feature/equality
branch
from
02c1fc7 to
633efd0
Compare
Member
Author
|
This should be better. |
no-reply
pushed a commit
that referenced
this pull request
Feb 21, 2016
Test literal equality handling on insert/delete
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.
When
:literal_equalityis supported, ensure that RDF term-equality is preserved on write operations.This does not avoid existing checks in the queryable shared examples. My thinking is that, with the interface established, it will be easier to root these out; in the meanwhile, identifying and handling them shouldn't be a blocker for 2.0 releases.