New Aura and Cypher page #435
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
added 3 commits
February 21, 2023 11:49
JPryce-Aklundh
added
the
cherry-pick-this-to-5.x
Collaborator
|
Looks like you've updated the documentation! Check out your changes at https://neo4j-docs-cypher-435.surge.sh |
davidoliverSP2
approved these changes
Feb 22, 2023
Contributor
davidoliverSP2
left a comment
davidoliverSP2
left a comment
There was a problem hiding this comment.
Thanks @JPryce-Aklundh
A couple of other editorial suggestions to consider 👍
MarkWoulfeNeo4j
approved these changes
Feb 22, 2023
Contributor
MarkWoulfeNeo4j
left a comment
MarkWoulfeNeo4j
left a comment
There was a problem hiding this comment.
small wording tweaks but purely opinionated feedback
Comment on lines
26
to
32
| Most Cypher features are available on all tiers of Aura. | ||
| There are, however, some features which are not available on any Aura instance. | ||
| For example, it is not possible to create, alter, or drop databases using Aura, nor is it possible to alter or drop servers. | ||
|
|
||
| There are also certain Cypher features which are only available on AuraDB Enterprise. | ||
| These can be categorized as the role-based access-control features of Cypher. | ||
| For example, it is not possible to create, alter, or drop roles using AuraDB Free, AuraDB Pro, AuraDS Pro, or AuraDS Enterprise, but it is possible using AuraDB Enterprise. |
Contributor
There was a problem hiding this comment.
Suggested change
| Most Cypher features are available on all tiers of Aura. | |
| There are, however, some features which are not available on any Aura instance. | |
| For example, it is not possible to create, alter, or drop databases using Aura, nor is it possible to alter or drop servers. | |
| There are also certain Cypher features which are only available on AuraDB Enterprise. | |
| These can be categorized as the role-based access-control features of Cypher. | |
| For example, it is not possible to create, alter, or drop roles using AuraDB Free, AuraDB Pro, AuraDS Pro, or AuraDS Enterprise, but it is possible using AuraDB Enterprise. | |
| Most Cypher functionality works across all tiers of Aura. | |
| There are, however, some parts of Cypher which are not available to Aura instances. | |
| For example, it is not possible to create, alter, or drop databases using Aura, nor is it possible to alter or drop servers. | |
| There are also certain Cypher features which are only available on AuraDB Enterprise instances. | |
| These can be categorized as the role-based access-control features of Cypher. | |
| For example, it is not possible to create, alter, or drop roles using AuraDB Free, AuraDB Pro, AuraDS Pro, or AuraDS Enterprise, but it is possible using AuraDB Enterprise. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
New page in the introduction of the Cypher Manual intended for Aura users.
The purpose of the page is to:
Content of role labels to be updated by the following PR in the docs-ui repo: https://github.com/neo4j-documentation/docs-ui/pull/150/files