Added DROP DATABASE name CASCADE ALIASES
#1036
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -103,8 +103,21 @@ label:new[] | |
| DROP [COMPOSITE] DATABASE ... [RESTRICT \| CASCADE ALIAS[ES]] | ||
| ---- | ||
|
|
||
| | Added the ability to drop database aliases while deleting a database. | ||
| This will affect local database aliases targeting the database and constituent database aliases belonging to the composite database. | ||
| For more information, see link:{neo4j-docs-base-uri}/operations-manual/{page-version}/database-administration/standard-databases/delete-databases/#delete-databases-with-aliases[Delete a database with local database aliases targeting it] and link:{neo4j-docs-base-uri}/operations-manual/{page-version}/database-administration/composite-databases/delete-composite-databases/#composite-databases-delete-with-aliases[Delete a composite database with constituent database aliases]. | ||
|
|
||
| a| | ||
| label:functionality[] | ||
| label:new[] | ||
| [source, cypher, role=noheader] | ||
| ---- | ||
| LOAD CSV FROM 'azb://azb-account/azb-container/artists.csv' AS row | ||
| MERGE (a:Artist {name: row[1], year: toInteger(row[2])}) | ||
| RETURN a.name, a.year | ||
| ---- | ||
|
|
||
| | Extension of the xref:clauses/load-csv.adoc#azure-cloud-storage[LOAD CSV] clause to allow loading CSV files from Azure Cloud Storage URIs. | ||
|
There was a problem hiding this comment. feels weird that this is added as part of this PR... There was a problem hiding this comment. It wasnt - it was added here #1008 There was a problem hiding this comment. because you pull-merged instead of rebased XD |
||
|
|
||
| |=== | ||
|
|
||
|
|
||
Oops, something went wrong.
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.
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.
maybe?
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.
though I guess we are already pretty inconsistent if we write drop or delete 🤷
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.
You are right - we need to decide on which to use and stick with it. Personally I think we should use drop because that is what the command is called (otherwise I definitely would have preferred "delete"). I will bring this up with my Ops Manual colleagues and take a decision.