Skip to content

Commit 61614d5

Browse files
Hunternessrenetapopova
authored andcommitted
Add some sentences about default language and aliases
1 parent b786e36 commit 61614d5

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
@@ -18,6 +18,7 @@ CREATE DATABASE `perennial-flowers`;
1818
----
1919
////
2020

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

2223
[[manage-aliases-composite-databases-list]]
2324
== 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
@@ -16,9 +16,9 @@ For more information, see xref:database-administration/aliases/manage-aliases-co
1616

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

21-
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.
21+
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.
2222
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].
2323
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.
2424

@@ -290,6 +290,8 @@ SHOW ALIAS `northwind` FOR DATABASE
290290
+---------------------------------------------------------------------------+
291291
----
292292

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

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

361+
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.
362+
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.
363+
There is currently no command to set it explicitly nor change it on existing remote database aliases.
364+
359365
As with local database aliases, creating remote database aliases allows `IF NOT EXISTS` and `OR REPLACE` clauses.
360366
Both check for any remote or local database aliases.
361367

0 commit comments

Comments
 (0)