-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added relationship PBAC to the Deprecations, additions, and compatibility page #1239
base: dev
Are you sure you want to change the base?
Conversation
---- | ||
[source, cypher, role=noheader] | ||
---- | ||
GRANT TRAVERSE ON GRAPH * FOR ()-[r:Knows]-() WHERE r.classification IS NULL TO regularUsers |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the examples could follow the neo4j syntax recommendations https://neo4j.com/docs/cypher-manual/current/syntax/naming/#_recommendations :KNOWS
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just out of curiosity, do you know why the naming convention is camel-case for labels and uppercase for relationship types?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's a good question :) I don't have the answer.
@@ -42,6 +42,23 @@ CALL (i) { | |||
This option applies an exponential delay between retries for transaction batches failing due to transient errors, with an optional maximum retry duration, and handles failure based on a specified fallback error mode if the transaction does not succeed within the given time. | |||
For more information, see xref:subqueries/subqueries-in-transactions#on-error-retry[`CALL` subqueries in transactions -> `ON ERROR RETRY`]. | |||
|
|||
a| |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
did you add this in the Neo4j 2025.03
section? cause I don't think that'll be the correct one XD
should probably add a section for the next version/the version we think it'll go GA in instead
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh, yes. Should be 2025.04 section. Was wrongly assuming that the newest section would be the latest, but I guess nothing else in cypher went into 2025.04 (at least not documented yet)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah, if you're first out you need to update it :P
also is 2025.04 correct? won't it still be behind a feature flag there and therefore not GA/documented? so it should be in 2025.05 (assuming we remove the feature flag in the next release)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
or did we remove the feature flag in the version just cutoff?
modules/ROOT/pages/deprecations-additions-removals-compatibility.adoc
Outdated
Show resolved
Hide resolved
modules/ROOT/pages/deprecations-additions-removals-compatibility.adoc
Outdated
Show resolved
Hide resolved
This PR includes documentation updates Updated pages: |
Documentation for the feature is in this PR: neo4j/docs-operations#2255