Skip to content

Commit 9372ad9

Browse files
committed
Add some sentences about default language and aliases
1 parent 706ff0a commit 9372ad9

File tree

2 files changed

+9
-2
lines changed

2 files changed

+9
-2
lines changed

modules/ROOT/pages/database-administration/aliases/manage-aliases-composite-databases.adoc

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,7 @@ CREATE DATABASE `perennial-flowers`;
1717
----
1818
////
1919

20+
Aliases in composite databases cannot be assigned default languages, they will always get the default from the composite database.
2021

2122
[[manage-aliases-composite-databases-list]]
2223
== List database aliases in composite databases

modules/ROOT/pages/database-administration/aliases/manage-aliases-standard-databases.adoc

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -15,9 +15,9 @@ For more information, see xref:database-administration/aliases/manage-aliases-co
1515

1616
A local database alias can be used in all other Cypher commands in place of the target database.
1717
Please note that the local database alias will be resolved while executing the command.
18-
Privileges are defined on the database, and not the local database alias.
18+
Privileges and default language are defined on the database, and not the local database alias.
1919

20-
A remote database alias can be used for connecting to a database of a remote Neo4j DBMS, `USE` clauses, setting a user's home database, and defining the access privileges to the remote database.
20+
A remote database alias can be used for connecting to a database of a remote Neo4j DBMS, `USE` clauses, setting a user's home database, and defining the access privileges and default language for queries to the remote database.
2121
Remote database aliases require configuration to safely connect to the remote target, which is described in xref::database-administration/aliases/remote-database-alias-configuration.adoc[Connecting remote databases].
2222
It is not possible to impersonate a user on the remote database or to execute an administration command on the remote database via a remote database alias.
2323

@@ -289,6 +289,8 @@ SHOW ALIAS `northwind` FOR DATABASE
289289
+---------------------------------------------------------------------------+
290290
----
291291

292+
Local database aliases cannot be assigned default languages, they will always get the default from their target database.
293+
292294
=== Use `IF EXISTS` or `OR REPLACE` when creating database aliases
293295

294296
The `CREATE ALIAS` command is optionally idempotent, with the default behavior to fail with an error if the database alias already exists.
@@ -355,6 +357,10 @@ SHOW ALIAS `northwind-2022` FOR DATABASE YIELD name, properties
355357
A database alias can target a remote database by providing an URL and the credentials of a user on the remote Neo4j DBMS.
356358
See xref:database-administration/aliases/remote-database-alias-configuration.adoc[] for the necessary configurations.
357359

360+
Since remote database aliases target databases that are not in this DBMS, they do not fetch the default language from their target like the local database aliases.
361+
Instead, remote database aliases are assigned the default language given by xref:configuration/configuration-settings.adoc#config_db.query.default_language[`db.query.default_language`] on creation.
362+
There is currently no command to set it explicitly nor change it on existing remote database aliases.
363+
358364
As with local database aliases, creating remote database aliases allows `IF NOT EXISTS` and `OR REPLACE` clauses.
359365
Both check for any remote or local database aliases.
360366

0 commit comments

Comments
 (0)