Fix Issue 1988: How to update a property which is a keyword #2005
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
github-actions
bot
added
master
override-stale
jrgemignani
force-pushed
the
allow_backticked_keywords
branch
from
00f62e5 to
e068b6d
Compare
MuhammadTahaNaveed
approved these changes
Aug 6, 2024
Fixed issue 1988: Reserved Keyword Handling: How to update a property
which is a keyword. Basically, how to use a keyword, aka reserved
word, in a query.
Added the appropriate scanner and parser rules to allow keywords to
be back ticked and used in queries as their name. For example, like
in the following commands -
MATCH (n:Person { id: 123 }) SET n.`match` = 'matched' RETURN n;
MATCH (n:Person { id: 123 }) SET n.`create` = 'created' RETURN n;
The changes did not break any regression tests.
Added additional regression tests.
jrgemignani
force-pushed
the
allow_backticked_keywords
branch
from
e068b6d to
a74b298
Compare
jrgemignani
added a commit
to jrgemignani/age
that referenced
this pull request
Aug 6, 2024
) Fixed issue 1988: Reserved Keyword Handling: How to update a property which is a keyword. Basically, how to use a keyword, aka reserved word, in a query. Added the appropriate scanner and parser rules to allow keywords to be back ticked and used in queries as their name. For example, like in the following commands - MATCH (n:Person { id: 123 }) SET n.`match` = 'matched' RETURN n; MATCH (n:Person { id: 123 }) SET n.`create` = 'created' RETURN n; The changes did not break any regression tests. Added additional regression tests.
jrgemignani
added a commit
to jrgemignani/age
that referenced
this pull request
Aug 6, 2024
) Fixed issue 1988: Reserved Keyword Handling: How to update a property which is a keyword. Basically, how to use a keyword, aka reserved word, in a query. Added the appropriate scanner and parser rules to allow keywords to be back ticked and used in queries as their name. For example, like in the following commands - MATCH (n:Person { id: 123 }) SET n.`match` = 'matched' RETURN n; MATCH (n:Person { id: 123 }) SET n.`create` = 'created' RETURN n; The changes did not break any regression tests. Added additional regression tests.
jrgemignani
added a commit
to jrgemignani/age
that referenced
this pull request
Aug 6, 2024
) Fixed issue 1988: Reserved Keyword Handling: How to update a property which is a keyword. Basically, how to use a keyword, aka reserved word, in a query. Added the appropriate scanner and parser rules to allow keywords to be back ticked and used in queries as their name. For example, like in the following commands - MATCH (n:Person { id: 123 }) SET n.`match` = 'matched' RETURN n; MATCH (n:Person { id: 123 }) SET n.`create` = 'created' RETURN n; The changes did not break any regression tests. Added additional regression tests.
jrgemignani
added a commit
to jrgemignani/age
that referenced
this pull request
Aug 6, 2024
) Fixed issue 1988: Reserved Keyword Handling: How to update a property which is a keyword. Basically, how to use a keyword, aka reserved word, in a query. Added the appropriate scanner and parser rules to allow keywords to be back ticked and used in queries as their name. For example, like in the following commands - MATCH (n:Person { id: 123 }) SET n.`match` = 'matched' RETURN n; MATCH (n:Person { id: 123 }) SET n.`create` = 'created' RETURN n; The changes did not break any regression tests. Added additional regression tests.
rafsun42
pushed a commit
that referenced
this pull request
Aug 6, 2024
…2017) Fixed issue 1988: Reserved Keyword Handling: How to update a property which is a keyword. Basically, how to use a keyword, aka reserved word, in a query. Added the appropriate scanner and parser rules to allow keywords to be back ticked and used in queries as their name. For example, like in the following commands - MATCH (n:Person { id: 123 }) SET n.`match` = 'matched' RETURN n; MATCH (n:Person { id: 123 }) SET n.`create` = 'created' RETURN n; The changes did not break any regression tests. Added additional regression tests.
rafsun42
pushed a commit
that referenced
this pull request
Aug 6, 2024
…2016) Fixed issue 1988: Reserved Keyword Handling: How to update a property which is a keyword. Basically, how to use a keyword, aka reserved word, in a query. Added the appropriate scanner and parser rules to allow keywords to be back ticked and used in queries as their name. For example, like in the following commands - MATCH (n:Person { id: 123 }) SET n.`match` = 'matched' RETURN n; MATCH (n:Person { id: 123 }) SET n.`create` = 'created' RETURN n; The changes did not break any regression tests. Added additional regression tests.
rafsun42
pushed a commit
that referenced
this pull request
Aug 6, 2024
…2015) Fixed issue 1988: Reserved Keyword Handling: How to update a property which is a keyword. Basically, how to use a keyword, aka reserved word, in a query. Added the appropriate scanner and parser rules to allow keywords to be back ticked and used in queries as their name. For example, like in the following commands - MATCH (n:Person { id: 123 }) SET n.`match` = 'matched' RETURN n; MATCH (n:Person { id: 123 }) SET n.`create` = 'created' RETURN n; The changes did not break any regression tests. Added additional regression tests.
rafsun42
pushed a commit
that referenced
this pull request
Aug 6, 2024
…2014) Fixed issue 1988: Reserved Keyword Handling: How to update a property which is a keyword. Basically, how to use a keyword, aka reserved word, in a query. Added the appropriate scanner and parser rules to allow keywords to be back ticked and used in queries as their name. For example, like in the following commands - MATCH (n:Person { id: 123 }) SET n.`match` = 'matched' RETURN n; MATCH (n:Person { id: 123 }) SET n.`create` = 'created' RETURN n; The changes did not break any regression tests. Added additional regression tests.
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.
Fixed issue 1988: Reserved Keyword Handling: How to update a property which is a keyword. Basically, how to use a keyword, aka reserved word, in a query.
Added the appropriate scanner and parser rules to allow keywords to be back ticked and used in queries as their name. For example, like in the following commands -
The changes did not break any regression tests.
Added additional regression tests.