Added DROP DATABASE name CASCADE ALIASES
#1036
Conversation
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
…ty.adoc Co-authored-by: Jens Pryce-Åklundh <[email protected]>
|
Thanks for the documentation updates. The preview documentation has now been torn down - reopening this PR will republish it. |
| @@ -103,8 +103,21 @@ label:new[] | |||
| DROP [COMPOSITE] DATABASE ... [RESTRICT \| CASCADE ALIAS[ES]] | |||
| ---- | |||
|
|
|||
| | Added the ability to drop any database aliases, that would otherwise block the deletion of the database, at the same time as the deletion of the database. | |||
| | Added the ability to drop database aliases while deleting a database. | |||
There was a problem hiding this comment.
| | Added the ability to drop database aliases while deleting a database. | |
| | Added the ability to drop database aliases while dropping a database. |
maybe?
There was a problem hiding this comment.
though I guess we are already pretty inconsistent if we write drop or delete 🤷
There was a problem hiding this comment.
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.
| 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
It appeared in this PR because I had to resolve a conflict
There was a problem hiding this comment.
because you pull-merged instead of rebased XD
Companion Pr to neo4j/docs-operations#1805, ~~should probably wait for that to go in.~~ Documenting neo-technology/neo4j#26465, ~~needs to wait until that has been merged.~~ --------- Co-authored-by: Jens Pryce-Åklundh <[email protected]>
Companion Pr to neo4j/docs-operations#1805,
should probably wait for that to go in.Documenting https://github.com/neo-technology/neo4j/pull/26465,
needs to wait until that has been merged.