You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/ROOT/pages/database-administration/aliases/manage-aliases-standard-databases.adoc
+8-2Lines changed: 8 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,9 +16,9 @@ For more information, see xref:database-administration/aliases/manage-aliases-co
16
16
17
17
A local database alias can be used in all other Cypher commands in place of the target database.
18
18
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.
20
20
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.
22
22
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].
23
23
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.
24
24
@@ -290,6 +290,8 @@ SHOW ALIAS `northwind` FOR DATABASE
Local database aliases cannot be assigned default languages, they will always get the default from their target database.
294
+
293
295
=== Use `IF EXISTS` or `OR REPLACE` when creating database aliases
294
296
295
297
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
356
358
A database alias can target a remote database by providing an URL and the credentials of a user on the remote Neo4j DBMS.
357
359
See xref:database-administration/aliases/remote-database-alias-configuration.adoc[] for the necessary configurations.
358
360
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
+
359
365
As with local database aliases, creating remote database aliases allows `IF NOT EXISTS` and `OR REPLACE` clauses.
360
366
Both check for any remote or local database aliases.
0 commit comments