Add DROP DATABASE name CASCADE ALIASES

modules/ROOT/pages/database-administration/composite-databases/delete-composite-databases.adoc

@@ -3,7 +3,7 @@
 [[composite-databases-delete]]
 = Delete composite databases
 
-You can delete composite databases using either the command `DROP COMPOSITE DATABASE name` or the more general one  `DROP DATABASE name`.
+You can delete composite databases using either the command `DROP COMPOSITE DATABASE name` or the more general one `DROP DATABASE name`.
 However, keep in mind that the first command will fail if the target database is not composite, while the second one will not fail because it targets any database.
 
 .Query
@@ -12,3 +12,37 @@ However, keep in mind that the first command will fail if the target database is
 DROP COMPOSITE DATABASE inventory
 ----
 
+[[composite-databases-delete-with-aliases]]
+== Delete a composite database with constituent database aliases
+
+In general, deleting a composite database that has constituent database aliases will fail as these aliases need to be dropped first.
+This applies to both the local and remote constituent database aliases belonging to the specified composite database.
+
+By appending `CASCADE ALIASES` to the command `DROP COMPOSITE DATABASE`, those constituent database aliases can be dropped alongside the composite database.
+This affects both the local and remote constituent database aliases belonging to the specified composite database.
+However, the behavior does not cascade further, the target of those constituent database aliases are not dropped.
+
+Using `CASCADE ALIASES` requires the `DROP ALIAS` privilege (see xref:authentication-authorization/dbms-administration.adoc#access-control-dbms-administration-alias-management[ALIAS MANAGEMENT privileges]).
+
+Given composite database and database alias:
+[source, cypher]
+----
+CREATE COMPOSITE DATABASE movies
+CREATE ALIAS movies.sweden FOR DATABASE `swedish-movies`
+----
+
+Then both the constituent database alias `sweden` and the composite database `movies` will be dropped with:
+[source, cypher]
+----
+DROP COMPOSITE DATABASE movies CASCADE ALIASES
+----
+
+This behavior would be the same for the more general command `DROP DATABASE name` when using it to drop a composite database.
+
+The option `RESTRICT` explicitly requests the default behavior of the command.
+
+[NOTE]
+====
+For composite databases, the aliases that will be dropped when using the `CASCADE ALIASES` option can be found in the `constituents` column of `SHOW DATABASE`.
+====
+

modules/ROOT/pages/database-administration/standard-databases/delete-databases.adoc

@@ -17,7 +17,7 @@ Note that all database aliases must be dropped before dropping a database.
 |
 [source, syntax, role="noheader"]
 ----
-DROP [COMPOSITE] DATABASE name [IF EXISTS] [{DUMP\|DESTROY} [DATA]] [WAIT [n [SEC[OND[S]]]]\|NOWAIT]
+DROP [COMPOSITE] DATABASE name [IF EXISTS] [RESTRICT \| CASCADE ALIAS[ES]] [{DUMP\|DESTROY} [DATA]] [WAIT [n [SEC[OND[S]]]]\|NOWAIT]
 ----
 
 |===
@@ -92,9 +92,9 @@ In Neo4j, dumps can be stored in the directory specified by the xref:configurati
 The option `DESTROY DATA` explicitly requests the default behavior of the command.
 
 [[delete-existing-db-with-dump]]
-=== Delete a database with `IF{nbsp}EXISTS` and  `DUMP DATA`/ `DESTROY DATA`
+=== Delete a database with `IF{nbsp}EXISTS` and  `DUMP DATA`/`DESTROY DATA`
 
-The options `IF EXISTS` and `DUMP DATA`/ `DESTROY DATA` can also be combined.
+The options `IF EXISTS` and `DUMP DATA`/`DESTROY DATA` can also be combined.
 
 An example could look like this:
 
@@ -103,4 +103,47 @@ An example could look like this:
 DROP DATABASE customers IF EXISTS DUMP DATA
 ----
 
+[[delete-databases-with-aliases]]
+=== Delete a database with local database aliases targeting it
+
+In general, deleting a database that is the target of any local database aliases will fail due as these aliases need to be dropped first.
+Remote database aliases targeting the database do not affect the deletion of the database.
+
+By appending `CASCADE ALIASES` to the command `DROP DATABASE`, those local database aliases can be dropped alongside the database.
+Any remote database aliases targeting the database will not be affected of the `CASCADE ALIASES`, they will simply no longer resolve their targets (which is the same behavior as if they are created targeting a non-existing database).
+However, the behavior does not cascade further, if any of the dropped database aliases are constituents to any composite database, those composite databases are not dropped.
+
+Using `CASCADE ALIASES` requires the `DROP ALIAS` privilege (see xref:authentication-authorization/dbms-administration.adoc#access-control-dbms-administration-alias-management[ALIAS MANAGEMENT privileges]).
+
+Given database and database alias:
+[source, cypher]
+----
+CREATE DATABASE movies
+CREATE ALIAS films FOR DATABASE movies
+----
+
+Then both the database alias `films` and the database `movies` will be dropped with:
+[source, cypher]
+----
+DROP DATABASE movies CASCADE ALIASES
+----
+
+The option `RESTRICT` explicitly requests the default behavior of the command.
+
+[NOTE]
+====
+For standard databases, the aliases that will be dropped when using the `CASCADE ALIASES` option can be found in the `aliases` column of `SHOW DATABASE`.
+====
+
+[[delete-existing-databases-with-aliases]]
+=== Delete a database with `RESTRICT`/`CASCADE ALIASES` and other command parts
+
+The options `RESTRICT`/`CASCADE ALIASES` can also be combined with `IF EXISTS` and `DUMP DATA`/`DESTROY DATA`.
+
+An example could look like this:
+
+[source, cypher]
+----
+DROP DATABASE movies IF EXISTS CASCADE ALIASES DUMP DATA
+----
 

modules/ROOT/pages/database-administration/syntax.adoc

@@ -176,7 +176,7 @@ START DATABASE name [WAIT [n [SEC[OND[S]]]]\|NOWAIT]
 |
 [source, syntax, role="noheader"]
 ----
-DROP [COMPOSITE] DATABASE name [IF EXISTS] [{DUMP\|DESTROY} [DATA]] [WAIT [n [SEC[OND[S]]]]\|NOWAIT]
+DROP [COMPOSITE] DATABASE name [IF EXISTS] [RESTRICT \| CASCADE ALIAS[ES]] [{DUMP\|DESTROY} [DATA]] [WAIT [n [SEC[OND[S]]]]\|NOWAIT]
 ----
 
 |===