Add optional parameter '=' in property constraints #1590
Merged
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
- The '=' operator checks if the original property value(as a whole) is
equal to the given value.
e.g MATCH (n {school:{addr:{city:'Toronto'}}}) tranforms into
either(in case age.enable_containment is off)
`properties.school.addr.city = 'Toronto'`
or(in case age.enable_containment is on)
`properties @> {school:{addr:{city:'Toronto'}}}`
But MATCH (n ={school:{addr:{city:'Toronto'}}}) will tranform into
either(in case age.enable_containment is off)
`properties.school = {addr:{city:'Toronto'}}`
or(in case age.enable_containment is on)
`properties @>> {school:{addr:{city:'Toronto'}}}`
- Added @>> and <<@ operators. Unlike @> and <@, these operators does
not recurse into sub-objects.
- Added regression tests.
- Added changes in sql files to version update template file.
jrgemignani
approved these changes
Feb 12, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 '=' operator checks if the original property value(as a whole) is equal to the given value.
e.g MATCH (n {school:{addr:{city:'Toronto'}}}) tranforms into
Added @>> and <<@ operators. Unlike @> and <@, these operators does not recurse into sub-objects.
Added regression tests.