From 79621b3ca7a0b51e1d1444eb2c447d404a94f9b3 Mon Sep 17 00:00:00 2001 From: Reneta Popova Date: Wed, 20 May 2026 17:20:53 +0100 Subject: [PATCH 1/5] Replace list with show where possible --- .../attribute-based-access-control.adoc | 12 +++++------ .../database-administration.adoc | 4 ++-- .../dbms-administration/dbms-admin-role.adoc | 6 +++--- .../dbms-alias-management-privileges.adoc | 12 +++++------ .../dbms-auth-rule-management-privileges.adoc | 20 +++++++++---------- .../dbms-database-management-privileges.adoc | 20 +++++++++---------- .../dbms-execute-privileges.adoc | 20 +++++++++---------- .../dbms-impersonate-privileges.adoc | 4 ++-- .../dbms-privilege-management-privileges.adoc | 12 +++++------ .../dbms-role-management-privileges.adoc | 14 ++++++------- .../dbms-server-management-privileges.adoc | 4 ++-- .../dbms-setting-privileges.adoc | 12 +++++------ .../dbms-user-management-privileges.adoc | 18 ++++++++--------- .../dbms-administration/index.adoc | 2 +- .../manage-privileges.adoc | 18 ++++++++--------- .../manage-roles.adoc | 16 +++++++-------- .../manage-users.adoc | 12 +++++------ .../ROOT/pages/backup-restore/inspect.adoc | 10 +++++----- .../monitoring/show-databases-monitoring.adoc | 12 +++++------ .../monitoring/show-servers-monitoring.adoc | 4 ++-- .../disaster-recovery.adoc | 6 +++--- .../ROOT/pages/clustering/server-syntax.adoc | 6 +++--- modules/ROOT/pages/clustering/servers.adoc | 8 ++++---- .../ROOT/pages/configuration/neo4j-conf.adoc | 2 +- modules/ROOT/pages/configuration/ports.adoc | 2 +- .../pages/configuration/show-settings.adoc | 16 +++++++-------- .../manage-aliases-composite-databases.adoc | 2 +- .../manage-aliases-standard-databases.adoc | 8 ++++---- .../standard-databases/listing-databases.adoc | 6 +++--- modules/ROOT/pages/introduction.adoc | 2 +- .../pages/monitoring/background-jobs.adoc | 4 ++-- .../monitoring/connection-management.adoc | 4 ++-- .../pages/monitoring/query-management.adoc | 2 +- .../performance/index-configuration.adoc | 2 +- .../pages/procedures/built-in-procedures.adoc | 2 +- .../pages/procedures/call-procedures.adoc | 2 +- .../list-composite-databases.adoc | 4 ++-- .../querying-composite-databases.adoc | 2 +- .../listing-sharded-databases.adoc | 8 ++++---- 39 files changed, 160 insertions(+), 160 deletions(-) diff --git a/modules/ROOT/pages/authentication-authorization/attribute-based-access-control.adoc b/modules/ROOT/pages/authentication-authorization/attribute-based-access-control.adoc index b0ef4491be..50ab49a891 100644 --- a/modules/ROOT/pages/authentication-authorization/attribute-based-access-control.adoc +++ b/modules/ROOT/pages/authentication-authorization/attribute-based-access-control.adoc @@ -65,7 +65,7 @@ The `conditionExpression` can use any valid Cypher expression that evaluates to |=== | Function group | Functions -| List functions +| Show functions | link:{neo4j-docs-base-uri}/cypher-manual/current/functions/list/#functions-range[range()], link:{neo4j-docs-base-uri}/cypher-manual/current/functions/list/#functions-reduce[reduce()], link:{neo4j-docs-base-uri}/cypher-manual/current/functions/string/#functions-reverse[reverse()], link:{neo4j-docs-base-uri}/cypher-manual/current/functions/list/#functions-tail[tail()], link:{neo4j-docs-base-uri}/cypher-manual/current/functions/list/#functions-tobooleanlist[toBooleanList()], link:{neo4j-docs-base-uri}/cypher-manual/current/functions/list/#functions-tofloatlist[toFloatList()], link:{neo4j-docs-base-uri}/cypher-manual/current/functions/list/#functions-tointegerlist[toIntegerList()], link:{neo4j-docs-base-uri}/cypher-manual/current/functions/list/#functions-tostringlist[toStringList()] | Numeric functions @@ -233,14 +233,14 @@ The following example revokes the `reader` role from the auth rule `temporary_re REVOKE ROLE reader FROM AUTH RULE temporary_reader; ---- -== Listing auth rules +== Showing auth rules -You can list all auth rules using the Cypher command `SHOW AUTH RULES`. +You can show all auth rules using the Cypher command `SHOW AUTH RULES`. [NOTE] ==== The `SHOW AUTH RULES` command requires the `SHOW AUTH RULE` privilege. -See xref:authentication-authorization/dbms-administration/dbms-auth-rule-management-privileges.adoc#grant-list-auth-rule-privilege[Grant privilege to list auth rules] for details on how to grant this privilege. +See xref:authentication-authorization/dbms-administration/dbms-auth-rule-management-privileges.adoc#grant-list-auth-rule-privilege[Grant privilege to show auth rules] for details on how to grant this privilege. ==== `SHOW AUTH RULES` returns a table containing a single row per auth rule with the following columns: @@ -294,7 +294,7 @@ This column returns `null` if the executing user is missing or denied the `SHOW === Example 1: List auth rules -The following example lists all auth rules with their conditions, enablement, and assigned roles: +The following example shows all auth rules with their conditions, enablement, and assigned roles: [source, cypher, role=noplay] ---- @@ -359,7 +359,7 @@ It is also possible to use `SKIP` and `LIMIT` to paginate the results. === Example 3: List auth rules as commands -The following example lists the auth rules as commands: +The following example shows the auth rules as commands: [source, cypher, role=noplay] ---- diff --git a/modules/ROOT/pages/authentication-authorization/database-administration.adoc b/modules/ROOT/pages/authentication-authorization/database-administration.adoc index 26502ff3bf..52821e90b3 100644 --- a/modules/ROOT/pages/authentication-authorization/database-administration.adoc +++ b/modules/ROOT/pages/authentication-authorization/database-administration.adoc @@ -48,9 +48,9 @@ See also xref:authentication-authorization/immutable-roles-privileges.adoc[]. ** `CREATE NEW [PROPERTY] NAME` - allows property names to be created, so that nodes and relationships can have properties assigned with these names. ** `NAME [MANAGEMENT]` - allows all of the name management capabilities: node labels, relationship types, and property names. ** `ALL [[DATABASE] PRIVILEGES]` - allows access, index, constraint, and name management for the specified database or remote database alias. -** `SHOW TRANSACTION` - allows listing transactions and queries for the specified users on the specified database. +** `SHOW TRANSACTION` - allows showing transactions and queries for the specified users on the specified database. ** `TERMINATE TRANSACTION` - allows ending transactions and queries for the specified users on the specified database. -** `TRANSACTION [MANAGEMENT]` - allows listing and ending transactions and queries for the specified users on the specified database. +** `TRANSACTION [MANAGEMENT]` - allows showing and ending transactions and queries for the specified users on the specified database. * _name_ ** The database to associate the privilege with. diff --git a/modules/ROOT/pages/authentication-authorization/dbms-administration/dbms-admin-role.adoc b/modules/ROOT/pages/authentication-authorization/dbms-administration/dbms-admin-role.adoc index c47a3ec8d8..25d38ff81d 100644 --- a/modules/ROOT/pages/authentication-authorization/dbms-administration/dbms-admin-role.adoc +++ b/modules/ROOT/pages/authentication-authorization/dbms-administration/dbms-admin-role.adoc @@ -122,7 +122,7 @@ GRANT ROLE MANAGEMENT ON DBMS TO userAndRoleAdministrator; ---- + As a result, the `userAndRoleAdministrator` role has privileges that only allow user and role management. -. To list all privileges for the role `userAndRoleAdministrator` as commands, use the following query: +. To show all privileges for the role `userAndRoleAdministrator` as commands, use the following query: + [source, cypher, role=noplay] ---- @@ -177,7 +177,7 @@ GRANT TRANSACTION MANAGEMENT (*) ON DATABASE * TO customAdministrator; ---- + As a result, the `customAdministrator` role has privileges that include managing transactions and all DBMS privileges except creating, dropping, and modifying databases. -. To list all privileges for the role `customAdministrator` as commands, use the following query: +. To show all privileges for the role `customAdministrator` as commands, use the following query: + [source, cypher, role=noplay] ---- @@ -240,7 +240,7 @@ REVOKE GRANT ACCESS ON DATABASE * FROM newAdministrator; GRANT ACCESS ON DATABASE system TO newAdministrator; ---- -. To list all privileges for the role `newAdministrator` as commands, use the following query: +. To show all privileges for the role `newAdministrator` as commands, use the following query: + [source, cypher, role=noplay] ---- diff --git a/modules/ROOT/pages/authentication-authorization/dbms-administration/dbms-alias-management-privileges.adoc b/modules/ROOT/pages/authentication-authorization/dbms-administration/dbms-alias-management-privileges.adoc index 7d507f3da0..429e6c8785 100644 --- a/modules/ROOT/pages/authentication-authorization/dbms-administration/dbms-alias-management-privileges.adoc +++ b/modules/ROOT/pages/authentication-authorization/dbms-administration/dbms-alias-management-privileges.adoc @@ -125,7 +125,7 @@ GRANT CREATE ALIAS ON DBMS TO aliasAdder; ---- As a result, the `aliasAdder` role has privileges that only allow creating aliases. -To list all privileges for the role `aliasAdder` as commands, use the following query: +To show all privileges for the role `aliasAdder` as commands, use the following query: [source, cypher, role=noplay] ---- @@ -177,7 +177,7 @@ GRANT ALTER ALIAS ON DBMS TO aliasModifier; ---- As a result, the `aliasModifier` role has privileges that only allow modifying aliases. -To list all privileges for the role `aliasModifier` as commands, use the following query: +To show all privileges for the role `aliasModifier` as commands, use the following query: [source, cypher, role=noplay] ---- @@ -193,9 +193,9 @@ a|Rows: 1 |=== -== Grant privilege to list aliases +== Grant privilege to show aliases -You can grant the privilege to list aliases using the `SHOW ALIAS` privilege. + +You can grant the privilege to show aliases using the `SHOW ALIAS` privilege. + For example: [source, cypher, role=noplay] @@ -204,7 +204,7 @@ GRANT SHOW ALIAS ON DBMS TO aliasViewer; ---- As a result, the `aliasViewer` role has privileges that only allow modifying aliases. -To list all privileges for the role `aliasViewer` as commands, use the following query: +To show all privileges for the role `aliasViewer` as commands, use the following query: [source, cypher, role=noplay] ---- @@ -230,7 +230,7 @@ GRANT ALIAS MANAGEMENT ON DBMS TO aliasManager; ---- As a result, the `aliasManager` role has all privileges to manage aliases. -To list all privileges for the role `aliasManager` as commands, use the following query: +To show all privileges for the role `aliasManager` as commands, use the following query: [source, cypher, role=noplay] ---- diff --git a/modules/ROOT/pages/authentication-authorization/dbms-administration/dbms-auth-rule-management-privileges.adoc b/modules/ROOT/pages/authentication-authorization/dbms-administration/dbms-auth-rule-management-privileges.adoc index c838c390fc..60002a901a 100644 --- a/modules/ROOT/pages/authentication-authorization/dbms-administration/dbms-auth-rule-management-privileges.adoc +++ b/modules/ROOT/pages/authentication-authorization/dbms-administration/dbms-auth-rule-management-privileges.adoc @@ -78,7 +78,7 @@ GRANT CREATE AUTH RULE ON DBMS TO authRuleAdder; As a result, the `authRuleAdder` role has privileges that allow adding auth rules. -To list all privileges for the role `authRuleAdder` as commands, use the following query: +To show all privileges for the role `authRuleAdder` as commands, use the following query: [source, cypher, role=noplay] ---- @@ -106,7 +106,7 @@ GRANT RENAME AUTH RULE ON DBMS TO authRuleNameModifier; As a result, the `authRuleNameModifier` role has privileges that allow renaming auth rules. -To list all privileges for the role `authRuleNameModifier`, use the following query: +To show all privileges for the role `authRuleNameModifier`, use the following query: [source, cypher, role=noplay] ---- @@ -134,7 +134,7 @@ GRANT ALTER AUTH RULE ON DBMS TO authRuleModifier; As a result, the `authRuleModifier` role has privileges that allow modifying auth rules. -To list all privileges for the role `authRuleModifier`, use the following query: +To show all privileges for the role `authRuleModifier`, use the following query: [source, cypher, role=noplay] ---- @@ -170,7 +170,7 @@ GRANT DROP AUTH RULE ON DBMS TO authRuleDropper; As a result, the `authRuleDropper` role has privileges that allow deleting auth rules. -To list all privileges for the role `authRuleDropper`, use the following query: +To show all privileges for the role `authRuleDropper`, use the following query: [source, cypher, role=noplay] ---- @@ -186,9 +186,9 @@ a|Rows: 1 |=== [[grant-list-auth-rule-privilege]] -== Grant privilege to list auth rules +== Grant privilege to show auth rules -You can grant the privilege to list auth rules using the `SHOW AUTH RULE` privilege. +You can grant the privilege to show auth rules using the `SHOW AUTH RULE` privilege. A role with this privilege is allowed to execute the `SHOW AUTH RULES` administration commands. It also grants the role the ability to show auth rules assigned to roles with the `SHOW RULES WITH AUTH RULES` command. @@ -199,9 +199,9 @@ The following query shows an example of how to grant the `SHOW AUTH RULE` privil GRANT SHOW AUTH RULE ON DBMS TO authRuleViewer; ---- -As a result, the `authRuleViewer` role has privileges that allow listing auth rules. +As a result, the `authRuleViewer` role has privileges that allow showing auth rules. -To list all privileges for the role `authRuleViewer` as commands, use the following query: +To show all privileges for the role `authRuleViewer` as commands, use the following query: [source, cypher, role=noplay] ---- @@ -218,7 +218,7 @@ a|Rows: 1 == Grant privilege to manage auth rules -You can grant the privilege to create, rename, modify, delete, and list auth rules using the `AUTH RULE MANAGEMENT` privilege. + +You can grant the privilege to create, rename, modify, delete, and show auth rules using the `AUTH RULE MANAGEMENT` privilege. + For example: [source, cypher, role=noplay] @@ -228,7 +228,7 @@ GRANT AUTH RULE MANAGEMENT ON DBMS TO authRuleManager; As a result, the `authRuleManager` role has all privileges to manage auth rules. -To list all privileges for the role `authRuleManager` as commands, use the following query: +To show all privileges for the role `authRuleManager` as commands, use the following query: [source, cypher, role=noplay] ---- diff --git a/modules/ROOT/pages/authentication-authorization/dbms-administration/dbms-database-management-privileges.adoc b/modules/ROOT/pages/authentication-authorization/dbms-administration/dbms-database-management-privileges.adoc index 0738abbbbc..85a070949c 100644 --- a/modules/ROOT/pages/authentication-authorization/dbms-administration/dbms-database-management-privileges.adoc +++ b/modules/ROOT/pages/authentication-authorization/dbms-administration/dbms-database-management-privileges.adoc @@ -162,7 +162,7 @@ GRANT CREATE DATABASE ON DBMS TO databaseAdder ---- As a result, the `databaseAdder` role has privileges that only allow creating standard databases. -To list all privileges for the role `databaseAdder` as commands, use the following query: +To show all privileges for the role `databaseAdder` as commands, use the following query: [source, cypher, role=noplay] ---- @@ -188,7 +188,7 @@ GRANT CREATE COMPOSITE DATABASE ON DBMS TO compositeDatabaseAdder ---- As a result, the `compositeDatabaseAdder` role has privileges that only allow creating composite databases. -To list all privileges for the role `compositeDatabaseAdder` as commands, use the following query: +To show all privileges for the role `compositeDatabaseAdder` as commands, use the following query: [source, cypher, role=noplay] ---- @@ -214,7 +214,7 @@ GRANT DROP DATABASE ON DBMS TO databaseDropper ---- As a result, the `databaseDropper` role has privileges that only allow deleting standard databases. -To list all privileges for the role `databaseDropper` as commands, use the following query: +To show all privileges for the role `databaseDropper` as commands, use the following query: [source, cypher, role=noplay] ---- @@ -240,7 +240,7 @@ GRANT DROP COMPOSITE DATABASE ON DBMS TO compositeDatabaseDropper ---- As a result, the `compositeDatabaseDropper` role has privileges that only allow deleting composite databases. -To list all privileges for the role `compositeDatabaseDropper` as commands, use the following query: +To show all privileges for the role `compositeDatabaseDropper` as commands, use the following query: [source, cypher, role=noplay] ---- @@ -266,7 +266,7 @@ GRANT ALTER DATABASE ON DBMS TO databaseModifier; ---- As a result, the `databaseModifier` role has privileges that only allow modifying standard databases. -To list all privileges for the role `databaseModifier` as commands, use the following query: +To show all privileges for the role `databaseModifier` as commands, use the following query: [source, cypher, role=noplay] ---- @@ -299,7 +299,7 @@ GRANT SET DATABASE ACCESS ON DBMS TO accessModifier ---- As a result, the `accessModifier` role has privileges that only allow modifying access to standard databases. -To list all privileges for the role `accessModifier` as commands, use the following query: +To show all privileges for the role `accessModifier` as commands, use the following query: [source, cypher, role=noplay] ---- @@ -333,7 +333,7 @@ GRANT SET DATABASE DEFAULT LANGUAGE ON DBMS TO languageModifier ---- As a result, the `languageModifier` role has privileges that only allow modifying default language to standard databases. -To list all privileges for the role `languageModifier` as commands, use the following query: +To show all privileges for the role `languageModifier` as commands, use the following query: [source, cypher, role=noplay] ---- @@ -368,7 +368,7 @@ GRANT ALTER COMPOSITE DATABASE ON DBMS TO compositeDatabaseModifier; ---- As a result, the `compositeDatabaseModifier` role has privileges that only allow modifying composite databases. -To list all privileges for the role `compositeDatabaseModifier` as commands, use the following query: +To show all privileges for the role `compositeDatabaseModifier` as commands, use the following query: [source, cypher, role=noplay] ---- @@ -401,7 +401,7 @@ GRANT COMPOSITE DATABASE MANAGEMENT ON DBMS TO compositeDatabaseManager; ---- As a result, the `compositeDatabaseManager` role has all privileges to manage composite databases. -To list all privileges for the role `compositeDatabaseManager` as commands, use the following query: +To show all privileges for the role `compositeDatabaseManager` as commands, use the following query: [source, cypher, role=noplay] ---- @@ -427,7 +427,7 @@ GRANT DATABASE MANAGEMENT ON DBMS TO databaseManager; ---- As a result, the `databaseManager` role has all privileges to manage standard and composite databases. -To list all privileges for the role `databaseManager` as commands, use the following query: +To show all privileges for the role `databaseManager` as commands, use the following query: [source, cypher, role=noplay] ---- diff --git a/modules/ROOT/pages/authentication-authorization/dbms-administration/dbms-execute-privileges.adoc b/modules/ROOT/pages/authentication-authorization/dbms-administration/dbms-execute-privileges.adoc index b4df653793..4972e88a7c 100644 --- a/modules/ROOT/pages/authentication-authorization/dbms-administration/dbms-execute-privileges.adoc +++ b/modules/ROOT/pages/authentication-authorization/dbms-administration/dbms-execute-privileges.adoc @@ -132,7 +132,7 @@ GRANT EXECUTE PROCEDURE db.schema.* ON DBMS TO procedureExecutor; Users with the role `procedureExecutor` can run any procedure in the `db.schema` namespace. The procedures are executed using the user's own privileges. -To list all privileges for the role `procedureExecutor` as commands, use the following query: +To show all privileges for the role `procedureExecutor` as commands, use the following query: [source, cypher, role=noplay] ---- @@ -165,7 +165,7 @@ DENY EXECUTE PROCEDURE dbms.cluster* ON DBMS TO deniedProcedureExecutor; Users with the role `deniedProcedureExecutor` can run any procedure except those starting with `dbms.cluster`. The procedures are executed using the user's own privileges. -To list all privileges for the role `deniedProcedureExecutor` as commands, use the following query: +To show all privileges for the role `deniedProcedureExecutor` as commands, use the following query: [source, cypher, role=noplay] ---- @@ -209,7 +209,7 @@ GRANT EXECUTE BOOSTED PROCEDURE db.labels, db.relationshipTypes ON DBMS TO boost Users with the role `boostedProcedureExecutor` can thus run the `db.labels` and the `db.relationshipTypes` procedures with full privileges, seeing everything in the graph and not just the labels and types that the user has `TRAVERSE` privilege on. Without the `EXECUTE PROCEDURE`, no procedures could be executed at all. -To list all privileges for the role `boostedProcedureExecutor` as commands, use the following query: +To show all privileges for the role `boostedProcedureExecutor` as commands, use the following query: [source, cypher, role=noplay] ---- @@ -243,7 +243,7 @@ As a result, the `deniedBoostedProcedureExecutor1` role has privileges that allo They also prevent the `db.labels` procedure from being elevated. Still, the denied `EXECUTE BOOSTED PROCEDURE` does not block execution of `db.labels`. -To list all privileges for role `deniedBoostedProcedureExecutor1` as commands, use the following query: +To show all privileges for role `deniedBoostedProcedureExecutor1` as commands, use the following query: [source, cypher, role=noplay] ---- @@ -278,7 +278,7 @@ DENY EXECUTE PROCEDURE db.labels ON DBMS TO deniedBoostedProcedureExecutor2; As a result, the `deniedBoostedProcedureExecutor2` role has privileges that allow elevating the privileges for all procedures, but cannot execute any due to missing or denied `EXECUTE PROCEDURE` privileges. -To list all privileges for the role `deniedBoostedProcedureExecutor2` as commands, use the following query: +To show all privileges for the role `deniedBoostedProcedureExecutor2` as commands, use the following query: [source, cypher, role=noplay] ---- @@ -315,7 +315,7 @@ DENY EXECUTE BOOSTED PROCEDURE db.labels ON DBMS TO deniedBoostedProcedureExecut As a result, the `deniedBoostedProcedureExecutor3` role has privileges that allow elevating the privileges for all procedures except `db.labels`. However, no procedures can be executed due to missing `EXECUTE PROCEDURE` privilege. -To list all privileges for the role `deniedBoostedProcedureExecutor3` as commands, use the following query: +To show all privileges for the role `deniedBoostedProcedureExecutor3` as commands, use the following query: [source, cypher, role=noplay] ---- @@ -372,7 +372,7 @@ GRANT EXECUTE ADMIN PROCEDURES ON DBMS TO adminProcedureExecutor; Users with the role `adminProcedureExecutor` can run any `admin` procedure with elevated privileges. As a result, the `adminProcedureExecutor` role has privileges that allow the execution of all admin procedures. -To list all privileges for the role `adminProcedureExecutor` as commands, use the following query: +To show all privileges for the role `adminProcedureExecutor` as commands, use the following query: [source, cypher, role=noplay] ---- @@ -428,7 +428,7 @@ Users with the role `functionExecutor` can thus run any UDF in the `apoc.coll` n The functions are executed using the user's own privileges. As a result, the `functionExecutor` role has privileges that only allow executing UDFs in the `apoc.coll` namespace. -To list all privileges for the role `functionExecutor` as commands, use the following query: +To show all privileges for the role `functionExecutor` as commands, use the following query: [source,cypher,role=noplay] ---- @@ -472,7 +472,7 @@ DENY EXECUTE FUNCTION apoc.any.prop* ON DBMS TO deniedFunctionExecutor; As a result, the `deniedFunctionExecutor` role has privileges that only allow the execution of all UDFs except those starting with `apoc.any.prop`. The functions are executed using the user's own privileges. -To list all privileges for the role `deniedFunctionExecutor` as commands, use the following query: +To show all privileges for the role `deniedFunctionExecutor` as commands, use the following query: [source, cypher, role=noplay] ---- @@ -527,7 +527,7 @@ Users with the role `boostedFunctionExecutor` can thus run `apoc.any.properties` Without the `EXECUTE USER DEFINED FUNCTION`, you cannot execute any UDFs at all. As a result, the `boostedFunctionExecutor` role has privileges that allow executing the UDF `apoc.any.properties` with elevated privileges, and all other UDFs with the users' own privileges. -To list all privileges for the role `boostedFunctionExecutor` as commands, use the following query: +To show all privileges for the role `boostedFunctionExecutor` as commands, use the following query: [source,cypher,role=noplay] ---- diff --git a/modules/ROOT/pages/authentication-authorization/dbms-administration/dbms-impersonate-privileges.adoc b/modules/ROOT/pages/authentication-authorization/dbms-administration/dbms-impersonate-privileges.adoc index 4b2922e85f..d60dc36291 100644 --- a/modules/ROOT/pages/authentication-authorization/dbms-administration/dbms-impersonate-privileges.adoc +++ b/modules/ROOT/pages/authentication-authorization/dbms-administration/dbms-impersonate-privileges.adoc @@ -112,7 +112,7 @@ GRANT IMPERSONATE (*) ON DBMS TO allUserImpersonator ---- As a result, the `allUserImpersonator` role has privileges that allow impersonating all users. -To list all privileges for the role `allUserImpersonator` as commands, use the following query: +To show all privileges for the role `allUserImpersonator` as commands, use the following query: .Query [source, cypher, role=noplay] @@ -149,7 +149,7 @@ DENY IMPERSONATE (alice) ON DBMS TO userImpersonator; As a result, the `userImpersonator` user would be able to impersonate only `bob`. -To list all privileges for the role `userImpersonator` as commands, use the following query: +To show all privileges for the role `userImpersonator` as commands, use the following query: .Query [source, cypher, role=noplay] diff --git a/modules/ROOT/pages/authentication-authorization/dbms-administration/dbms-privilege-management-privileges.adoc b/modules/ROOT/pages/authentication-authorization/dbms-administration/dbms-privilege-management-privileges.adoc index d0f12109ed..4ac578213f 100644 --- a/modules/ROOT/pages/authentication-authorization/dbms-administration/dbms-privilege-management-privileges.adoc +++ b/modules/ROOT/pages/authentication-authorization/dbms-administration/dbms-privilege-management-privileges.adoc @@ -107,9 +107,9 @@ GRANT [IMMUTABLE] PRIVILEGE MANAGEMENT | Enables the specified roles to list, assign, and remove privileges. |=== -== Grant privilege to list privileges +== Grant privilege to show privileges -You can grant the `SHOW PRIVILEGE` privilege to allow a user to list privileges using the `SHOW PRIVILEGE`, `SHOW ROLE roleName PRIVILEGES`, and `SHOW USER username PRIVILEGES` administration commands. +You can grant the `SHOW PRIVILEGE` privilege to allow a user to show privileges using the `SHOW PRIVILEGE`, `SHOW ROLE roleName PRIVILEGES`, and `SHOW USER username PRIVILEGES` administration commands. The `SHOW USER username PRIVILEGES` command also requires the `SHOW USER` privilege. For example: @@ -120,7 +120,7 @@ GRANT SHOW PRIVILEGE ON DBMS TO privilegeViewer; ---- As a result, the `privilegeViewer` role has privileges that only allow showing privileges. -To list all privileges for the role `privilegeViewer` as commands, use the following query: +To show all privileges for the role `privilegeViewer` as commands, use the following query: [source, cypher, role=noplay] ---- @@ -155,7 +155,7 @@ GRANT ASSIGN PRIVILEGE ON DBMS TO privilegeAssigner; ---- As a result, the `privilegeAssigner` role has privileges that only allow assigning privileges. -To list all privileges for the role `privilegeAssigner` as commands, use the following query: +To show all privileges for the role `privilegeAssigner` as commands, use the following query: [source, cypher, role=noplay] ---- @@ -182,7 +182,7 @@ GRANT REMOVE PRIVILEGE ON DBMS TO privilegeRemover; ---- As a result, the `privilegeRemover` role has privileges that only allow removing privileges. -To list all privileges for the role `privilegeRemover` as commands, use the following query: +To show all privileges for the role `privilegeRemover` as commands, use the following query: [source, cypher, role=noplay] ---- @@ -208,7 +208,7 @@ GRANT PRIVILEGE MANAGEMENT ON DBMS TO privilegeManager; ---- As a result, the `privilegeManager` role has all privileges to manage privileges. -To list all privileges for the role `privilegeManager` as commands, use the following query: +To show all privileges for the role `privilegeManager` as commands, use the following query: [source, cypher, role=noplay] ---- diff --git a/modules/ROOT/pages/authentication-authorization/dbms-administration/dbms-role-management-privileges.adoc b/modules/ROOT/pages/authentication-authorization/dbms-administration/dbms-role-management-privileges.adoc index 8ca668eabc..4451d1d284 100644 --- a/modules/ROOT/pages/authentication-authorization/dbms-administration/dbms-role-management-privileges.adoc +++ b/modules/ROOT/pages/authentication-authorization/dbms-administration/dbms-role-management-privileges.adoc @@ -138,7 +138,7 @@ GRANT CREATE ROLE ON DBMS TO roleAdder; As a result, the `roleAdder` role has privileges that only allow adding roles. -To list all privileges for the role `roleAdder` as commands, use the following query: +To show all privileges for the role `roleAdder` as commands, use the following query: [source, cypher, role=noplay] ---- @@ -165,7 +165,7 @@ GRANT RENAME ROLE ON DBMS TO roleNameModifier; As a result, the `roleNameModifier` role has privileges that only allow renaming roles. -To list all privileges for the role `roleNameModifier`, use the following query: +To show all privileges for the role `roleNameModifier`, use the following query: [source, cypher, role=noplay] ---- @@ -192,7 +192,7 @@ GRANT DROP ROLE ON DBMS TO roleDropper; As a result, the `roleDropper` role has privileges that only allow deleting roles. -To list all privileges for the role `roleDropper`, use the following query: +To show all privileges for the role `roleDropper`, use the following query: [source, cypher, role=noplay] ---- @@ -220,7 +220,7 @@ GRANT ASSIGN ROLE ON DBMS TO roleAssigner; As a result, the `roleAssigner` role has privileges that only allow assigning/granting roles. -To list all privileges for the role `roleAssigner` as commands, use the following query: +To show all privileges for the role `roleAssigner` as commands, use the following query: [source, cypher, role=noplay] ---- @@ -248,7 +248,7 @@ GRANT REMOVE ROLE ON DBMS TO roleRemover; As a result, the `roleRemover` role has privileges that only allow removing/revoking roles. -To list all privileges for the role `roleRemover` as commands, use the following query: +To show all privileges for the role `roleRemover` as commands, use the following query: [source, cypher, role=noplay] ---- @@ -288,7 +288,7 @@ GRANT SHOW ROLE ON DBMS TO roleViewer; As a result, the `roleViewer` role has privileges that only allow showing roles. -To list all privileges for the role `roleViewer` as commands, use the following query: +To show all privileges for the role `roleViewer` as commands, use the following query: [source, cypher, role=noplay] ---- @@ -315,7 +315,7 @@ GRANT ROLE MANAGEMENT ON DBMS TO roleManager; As a result, the `roleManager` role has all privileges to manage roles. -To list all privileges for the role `roleManager` as commands, use the following query: +To show all privileges for the role `roleManager` as commands, use the following query: [source, cypher, role=noplay] ---- diff --git a/modules/ROOT/pages/authentication-authorization/dbms-administration/dbms-server-management-privileges.adoc b/modules/ROOT/pages/authentication-authorization/dbms-administration/dbms-server-management-privileges.adoc index 1a6c3aea23..90de9633b1 100644 --- a/modules/ROOT/pages/authentication-authorization/dbms-administration/dbms-server-management-privileges.adoc +++ b/modules/ROOT/pages/authentication-authorization/dbms-administration/dbms-server-management-privileges.adoc @@ -106,7 +106,7 @@ GRANT SERVER MANAGEMENT ON DBMS TO serverManager; ---- As a result, the `serverManager` role has all privileges to manage servers. -To list all privileges for the role `serverManager` as commands, use the following query: +To show all privileges for the role `serverManager` as commands, use the following query: [source, cypher, role=noplay] ---- @@ -133,7 +133,7 @@ GRANT SHOW SERVERS ON DBMS TO serverViewer; ---- As a result, the `serverViewer` role has privileges that only allow showing servers. -To list all privileges for the role `serverViewer` as commands, use the following query: +To show all privileges for the role `serverViewer` as commands, use the following query: [source, cypher, role=noplay] ---- diff --git a/modules/ROOT/pages/authentication-authorization/dbms-administration/dbms-setting-privileges.adoc b/modules/ROOT/pages/authentication-authorization/dbms-administration/dbms-setting-privileges.adoc index a98f845452..96228b41bd 100644 --- a/modules/ROOT/pages/authentication-authorization/dbms-administration/dbms-setting-privileges.adoc +++ b/modules/ROOT/pages/authentication-authorization/dbms-administration/dbms-setting-privileges.adoc @@ -71,7 +71,7 @@ CREATE ROLE serverViewer IF NOT EXISTS; //// You can grant the privilege to show configuration settings using the `SHOW SETTING` privilege. -A role with this privilege is allowed to list the configuration settings matched by the xref:authentication-authorization/dbms-administration/index.adoc#access-control-name-globbing[name-globbing]. +A role with this privilege is allowed to show the configuration settings matched by the xref:authentication-authorization/dbms-administration/index.adoc#access-control-name-globbing[name-globbing]. [NOTE] ==== @@ -103,8 +103,8 @@ GRANT SHOW SETTING server.bolt.* ON DBMS TO configurationViewer; Users with the role `configurationViewer` can then view any setting in the `server.bolt` namespace. -As a result, the `configurationViewer` role has privileges that only allow listing settings in the `server.bolt` namespace. -To list all privileges for the role `configurationViewer` as commands, use the following query: +As a result, the `configurationViewer` role has privileges that only allow showing settings in the `server.bolt` namespace. +To show all privileges for the role `configurationViewer` as commands, use the following query: [source, cypher, role=noplay] ---- @@ -134,8 +134,8 @@ GRANT SHOW SETTINGS * ON DBMS TO deniedConfigurationViewer; DENY SHOW SETTING dbms.security* ON DBMS TO deniedConfigurationViewer; ---- -As a result, the `deniedConfigurationViewer` role has privileges that allow listing all settings except those starting with `dbms.security`. -To list all privileges for the role `deniedConfigurationViewer` as commands, use the following query: +As a result, the `deniedConfigurationViewer` role has privileges that allow showing all settings except those starting with `dbms.security`. +To show all privileges for the role `deniedConfigurationViewer` as commands, use the following query: [source, cypher, role=noplay] ---- @@ -151,4 +151,4 @@ SHOW ROLE deniedConfigurationViewer PRIVILEGES AS COMMANDS; a|Rows: 2 |=== -As the query result shows, viewing settings starting with `dbms.security` is blocked, but the rest can still be listed. \ No newline at end of file +As the query result shows, viewing settings starting with `dbms.security` is blocked, but the rest can still be shown. \ No newline at end of file diff --git a/modules/ROOT/pages/authentication-authorization/dbms-administration/dbms-user-management-privileges.adoc b/modules/ROOT/pages/authentication-authorization/dbms-administration/dbms-user-management-privileges.adoc index b73bcbdc17..1b65d2cc94 100644 --- a/modules/ROOT/pages/authentication-authorization/dbms-administration/dbms-user-management-privileges.adoc +++ b/modules/ROOT/pages/authentication-authorization/dbms-administration/dbms-user-management-privileges.adoc @@ -156,7 +156,7 @@ GRANT CREATE USER ON DBMS TO userAdder ---- As a result, the `userAdder` role has privileges that only allow adding users. -To list all privileges for the role `userAdder` as commands, use the following query: +To show all privileges for the role `userAdder` as commands, use the following query: [source, cypher, role=noplay] ---- @@ -182,7 +182,7 @@ GRANT RENAME USER ON DBMS TO userNameModifier ---- As a result, the `userNameModifier` role has privileges that only allow renaming users. -To list all privileges for the role `userNameModifier` as commands, use the following query: +To show all privileges for the role `userNameModifier` as commands, use the following query: [source, cypher, role=noplay] ---- @@ -208,7 +208,7 @@ GRANT ALTER USER ON DBMS TO userModifier ---- As a result, the `userModifier` role has privileges that only allow modifying users. -To list all privileges for the role `userModifier` as commands, use the following query: +To show all privileges for the role `userModifier` as commands, use the following query: [source, cypher, role=noplay] ---- @@ -248,7 +248,7 @@ GRANT SET PASSWORDS ON DBMS TO passwordModifier ---- As a result, the `passwordModifier` role has privileges that only allow modifying users' passwords and whether those passwords must be changed upon first login. -To list all privileges for the role `passwordModifier` as commands, use the following query: +To show all privileges for the role `passwordModifier` as commands, use the following query: [source, cypher, role=noplay] ---- @@ -301,7 +301,7 @@ GRANT SET USER STATUS ON DBMS TO statusModifier ---- As a result, the `statusModifier` role has privileges that only allow modifying the account status of users. -To list all privileges for the role `statusModifier` as commands, use the following query: +To show all privileges for the role `statusModifier` as commands, use the following query: [source, cypher, role=noplay] ---- @@ -334,7 +334,7 @@ GRANT SET USER HOME DATABASE ON DBMS TO homeDbModifier ---- As a result, the `homeDbModifier` role has privileges that only allow modifying the home database of users. -To list all privileges for the role `homeDbModifier` as commands, use the following query: +To show all privileges for the role `homeDbModifier` as commands, use the following query: [source, cypher, role=noplay] ---- @@ -374,7 +374,7 @@ GRANT DROP USER ON DBMS TO userDropper ---- As a result, the `userDropper` role has privileges that only allow deleting users. -To list all privileges for the role `userDropper` as commands, use the following query: +To show all privileges for the role `userDropper` as commands, use the following query: [source, cypher, role=noplay] ---- @@ -401,7 +401,7 @@ GRANT SHOW USER ON DBMS TO userViewer ---- As a result, the `userViewer` role has privileges that only allow showing users. -To list all privileges for the role `userViewer` as commands, use the following query: +To show all privileges for the role `userViewer` as commands, use the following query: [source, cypher, role=noplay] ---- @@ -427,7 +427,7 @@ GRANT USER MANAGEMENT ON DBMS TO userManager ---- As a result, the `userManager` role has all privileges to manage users. -To list all privileges for the role `userManager` as commands, use the following query: +To show all privileges for the role `userManager` as commands, use the following query: [source, cypher, role=noplay] ---- diff --git a/modules/ROOT/pages/authentication-authorization/dbms-administration/index.adoc b/modules/ROOT/pages/authentication-authorization/dbms-administration/index.adoc index a7d8ce7e42..0b71c526fa 100644 --- a/modules/ROOT/pages/authentication-authorization/dbms-administration/index.adoc +++ b/modules/ROOT/pages/authentication-authorization/dbms-administration/index.adoc @@ -118,7 +118,7 @@ For example, to grant the role `dbmsManager` all DBMS abilities, use the followi GRANT ALL DBMS PRIVILEGES ON DBMS TO dbmsManager; ---- -To list all privileges for the role `dbmsManager` as commands, use the following query: +To show all privileges for the role `dbmsManager` as commands, use the following query: [source, cypher, role=noplay] ---- diff --git a/modules/ROOT/pages/authentication-authorization/manage-privileges.adoc b/modules/ROOT/pages/authentication-authorization/manage-privileges.adoc index a2a6ea40cd..fa7afba4f6 100644 --- a/modules/ROOT/pages/authentication-authorization/manage-privileges.adoc +++ b/modules/ROOT/pages/authentication-authorization/manage-privileges.adoc @@ -228,10 +228,10 @@ image::privileges-hierarchy.svg[title="Graph privileges hierarchy", role=popup] [[access-control-list-supported-privileges]] -== Listing supported privileges +== Showing supported privileges Supported privileges can be displayed using the `SHOW SUPPORTED PRIVILEGES` command. -This lists the privileges that are possible to grant or deny on a server, together with the structure of the privilege. +It shows the privileges that are possible to grant or deny on a server, together with the structure of the privilege. .Show supported privileges command syntax [cols="<15s,<85"] @@ -305,7 +305,7 @@ Note that not all privileges have a scope. [[access-control-list-supported-privileges-example]] -=== Examples for listing supported privileges +=== Examples for showing supported privileges [source, cypher, role=noplay] ---- @@ -387,7 +387,7 @@ Lists 10 supported privileges: |=== [[access-control-list-privileges]] -== Listing assigned privileges +== Showing assigned privileges Privileges that have been granted or denied to roles can be displayed using the following `SHOW PRIVILEGE[S]` commands. @@ -531,7 +531,7 @@ Note that this is only returned for `SHOW USER [username] PRIVILEGES`. |=== [[access-control-list-all-privileges]] -=== Examples for listing all privileges +=== Examples for showing all privileges Assigned privileges can be displayed using the different `SHOW PRIVILEGE[S]` commands. @@ -1212,7 +1212,7 @@ WHERE command CONTAINS 'MANAGEMENT' a|Rows: 8 |=== -It is also possible to get the privileges listed as revoking commands instead of granting or denying: +It is also possible to show the privileges as revoking commands instead of granting or denying: [source, cypher, role=noplay] ---- @@ -1264,7 +1264,7 @@ a|Rows: 35 For more info about revoking privileges, please see xref:authentication-authorization/manage-privileges.adoc#access-control-revoke-privileges[The REVOKE command]. [[access-control-list-privileges-role]] -=== Examples for listing privileges for specific roles +=== Examples for showing privileges for specific roles Available privileges for specific roles can be displayed using `SHOW ROLE name PRIVILEGE[S]`: @@ -1386,7 +1386,7 @@ SHOW ROLE architect PRIVILEGES AS COMMANDS WHERE command CONTAINS 'MATCH' |Rows: 2 |=== -Again, it is possible to get the privileges listed as revoking commands instead of granting or denying. +Again, it is possible to show the privileges as revoking commands instead of granting or denying. For more info about revoking privileges, please see xref:authentication-authorization/manage-privileges.adoc#access-control-revoke-privileges[The REVOKE command]. [source, cypher, role=noplay] @@ -1405,7 +1405,7 @@ a|Rows: 3 |=== [[access-control-list-privileges-user]] -=== Examples for listing privileges for specific users +=== Examples for showing privileges for specific users Available privileges for specific users can be displayed using `SHOW USER name PRIVILEGES`. diff --git a/modules/ROOT/pages/authentication-authorization/manage-roles.adoc b/modules/ROOT/pages/authentication-authorization/manage-roles.adoc index 9815faeff2..a46360a7f2 100644 --- a/modules/ROOT/pages/authentication-authorization/manage-roles.adoc +++ b/modules/ROOT/pages/authentication-authorization/manage-roles.adoc @@ -53,7 +53,7 @@ Lists roles. When using the `RETURN` clause, the `YIELD` clause is mandatory and must not be omitted. -For more information, see xref:authentication-authorization/manage-roles.adoc#access-control-list-roles[Listing roles]. +For more information, see xref:authentication-authorization/manage-roles.adoc#access-control-list-roles[Showing roles]. | Required privilege a| @@ -89,7 +89,7 @@ Lists roles and users assigned to them. When using the `RETURN` clause, the `YIELD` clause is mandatory and must not be omitted. -For more information, see xref:authentication-authorization/manage-roles.adoc#access-control-list-roles[Listing roles]. +For more information, see xref:authentication-authorization/manage-roles.adoc#access-control-list-roles[Showing roles]. | Required privilege a| @@ -133,7 +133,7 @@ Lists roles and auth rules assigned to them. When using the `RETURN` clause, the `YIELD` clause is mandatory and must not be omitted. -For more information, see xref:authentication-authorization/manage-roles.adoc#access-control-list-roles[Listing roles]. +For more information, see xref:authentication-authorization/manage-roles.adoc#access-control-list-roles[Showing roles]. | Required privilege a| @@ -176,7 +176,7 @@ Lists the privileges granted to the specified roles. When using the `RETURN` clause, the `YIELD` clause is mandatory and must not be omitted. -The `SHOW ROLE name PRIVILEGES` command is described in xref:authentication-authorization/manage-privileges.adoc#access-control-list-privileges[Listing privileges]. +The `SHOW ROLE name PRIVILEGES` command is described in xref:authentication-authorization/manage-privileges.adoc#access-control-list-privileges[Showing privileges]. | Required privilege a| @@ -388,7 +388,7 @@ For more information, see xref:authentication-authorization/dbms-administration/ [[access-control-list-roles]] -== Listing roles +== Showing roles You can view all available roles using the Cypher command `SHOW ROLES`, which returns a single column by default. @@ -411,7 +411,7 @@ See <> for more information. | BOOLEAN |=== -=== Listing all roles +=== Showing all roles To list all roles, use the `SHOW ROLES` command: @@ -453,7 +453,7 @@ There are multiple versions of this command, the default being `SHOW ALL ROLES`. To only show roles that are assigned to users or auth rules, the command is `SHOW POPULATED ROLES`. This returns the same output columns as `SHOW ROLES`. -=== Listing users assigned to roles +=== Showing users assigned to roles To see which users are assigned to which roles, you can add `WITH USERS` to the command. @@ -493,7 +493,7 @@ If a role is assigned to multiple users, it will appear once for each user. |=== [role=label--new-2026.03] -=== Listing auth rules assigned to roles +=== Showing auth rules assigned to roles To see which auth rules are assigned to which roles, add `WITH AUTH RULES` to the command: diff --git a/modules/ROOT/pages/authentication-authorization/manage-users.adoc b/modules/ROOT/pages/authentication-authorization/manage-users.adoc index 9ea027b053..770736043e 100644 --- a/modules/ROOT/pages/authentication-authorization/manage-users.adoc +++ b/modules/ROOT/pages/authentication-authorization/manage-users.adoc @@ -85,7 +85,7 @@ Lists all users. When using the `RETURN` clause, the `YIELD` clause is mandatory and must not be omitted. -For more information, see xref:authentication-authorization/manage-users.adoc#access-control-list-users[Listing users]. +For more information, see xref:authentication-authorization/manage-users.adoc#access-control-list-users[Showing users]. | Required privilege a| @@ -120,7 +120,7 @@ Lists the privileges granted to the specified users or the current user if no us When using the `RETURN` clause, the `YIELD` clause is mandatory and must not be omitted. -The `SHOW USER name PRIVILEGES` command is described in xref:authentication-authorization/manage-privileges.adoc#access-control-list-privileges[Listing privileges]. +The `SHOW USER name PRIVILEGES` command is described in xref:authentication-authorization/manage-privileges.adoc#access-control-list-privileges[Showing privileges]. | Required privilege a| @@ -403,12 +403,12 @@ For more information, see xref:authentication-authorization/dbms-administration/ [NOTE,role=label--enterprise-edition] ==== -The `SHOW USER[S] PRIVILEGES` command is described in xref:authentication-authorization/manage-privileges.adoc#access-control-list-privileges[Listing privileges]. +The `SHOW USER[S] PRIVILEGES` command is described in xref:authentication-authorization/manage-privileges.adoc#access-control-list-privileges[Showing privileges]. ==== [[access-control-current-users]] -== Listing current user +== Showing current user You can view the currently logged-in user using the Cypher command `SHOW CURRENT USER`. It produces a table with the following columns: @@ -490,7 +490,7 @@ This command is only supported for a logged-in user and returns an empty result [[access-control-list-users]] -== Listing users +== Showing users You can list all available users using the Cypher command `SHOW USERS`. It produces a table containing a single row per user with the following columns: @@ -637,7 +637,7 @@ RETURN user AS adminUser ====== [[access-control-list-user-auth-providers]] -== Listing user auth providers +== Showing user auth providers To inspect available user auth providers, use `SHOW USERS WITH AUTH`. The command produces a row per user per auth provider and yields the following two columns in addition to those output by `SHOW USERS`: diff --git a/modules/ROOT/pages/backup-restore/inspect.adoc b/modules/ROOT/pages/backup-restore/inspect.adoc index 59450dd177..cc855b5d41 100644 --- a/modules/ROOT/pages/backup-restore/inspect.adoc +++ b/modules/ROOT/pages/backup-restore/inspect.adoc @@ -8,7 +8,7 @@ You can inspect the metadata of a database backup file using the `neo4j-admin ba [[inspect-backup-command]] == Command -The inspect command lists the metadata stored in the header of backup files. +The inspect command shows the metadata stored in the header of backup files. This metadata primarily defines how backups are connected to form xref:backup-restore/online-backup.adoc#backup-chain[backup chains]. A backup chain is a sequence of one or more backup(s) logically connected. The order of the sequence guarantees that when replayed (see xref:backup-restore/restore-backup.adoc[restore] or xref:backup-restore/aggregate.adoc[aggregate]), the store and the transaction data are consumed in a consistent manner. @@ -141,9 +141,9 @@ Given the folder _/backups_ containing a set of database backups: └── neo4j-2024-10-07T16-05-37.backup ---- -=== Listing the metadata of the backup files +=== Showing the metadata of the backup files -The following command lists the backup files' names along with their respective metadata: +The following command shows the backup files' names along with their respective metadata: [source,shell] ---- @@ -176,9 +176,9 @@ Starting with Neo4j 2025.07, the backup metadata is always shown by default when If you are on a previous version of Neo4j, you must specify the `--show-metadata` option to see the backup metadata. ==== -=== Listing the latest backups +=== Showing the latest backups -To list only the most recent backups performed for each database, use the `--latest-backup` option. +To show only the most recent backups performed for each database, use the `--latest-backup` option. [source,shell] ---- diff --git a/modules/ROOT/pages/clustering/monitoring/show-databases-monitoring.adoc b/modules/ROOT/pages/clustering/monitoring/show-databases-monitoring.adoc index 5fb664f464..a3f97e174e 100644 --- a/modules/ROOT/pages/clustering/monitoring/show-databases-monitoring.adoc +++ b/modules/ROOT/pages/clustering/monitoring/show-databases-monitoring.adoc @@ -7,7 +7,7 @@ In addition to the system-wide metrics and logs described in previous sections, [[show-databases-monitoring-listing]] -== Listing Databases +== Showing databases *Syntax:* @@ -51,7 +51,7 @@ See xref::database-administration/standard-databases/listing-databases.adoc#data Additionally, note that databases hosted on servers that are offline are also returned by the `SHOW DATABASES` command. For such databases the `address` column displays `NULL`, the `currentStatus` column displays `unknown`, and the `statusMessage` displays `Server is unavailable`. -.Listing databases in standalone Neo4j +.Showing databases in standalone Neo4j ==== When executing `SHOW DATABASES` against a standalone server, the following output is expected: @@ -70,7 +70,7 @@ In a standalone deployment with a single server, the `address` field should be t ==== -.Listing databases in a cluster +.Showing databases in a cluster ==== When running `SHOW DATABASES` against a cluster, expect similar output to the following: @@ -106,7 +106,7 @@ If a database is offline on a particular server, either because it was stopped b [[show-databases-monitoring-listing-single]] -== Listing a single database +== Showing a single database The number of rows returned by `SHOW DATABASES` can be quite large, especially when run in a cluster. You can filter the rows returned by database name (e.g. "foo") by using the command `SHOW DATABASE foo`. @@ -147,7 +147,7 @@ This node is either the leader for this database in a cluster _or_ this is a sta | constituents | List | A list of alias names making up this Composite database, null for non-Composite databases. |=== -.Listing statuses for database _foo_ +.Showing statuses for database _foo_ ==== When running `SHOW DATABASE foo` in a cluster, expect similar output to the following: @@ -163,7 +163,7 @@ When running `SHOW DATABASE foo` in a cluster, expect similar output to the foll ==== [[show-databases-monitoring-listing-expanded]] -== Listing more details about databases +== Showing more details about databases If more details about the databases are needed, `SHOW DATABASES` can be appended with `YIELD *`. diff --git a/modules/ROOT/pages/clustering/monitoring/show-servers-monitoring.adoc b/modules/ROOT/pages/clustering/monitoring/show-servers-monitoring.adoc index 2a49e7720b..a2d07b1a42 100644 --- a/modules/ROOT/pages/clustering/monitoring/show-servers-monitoring.adoc +++ b/modules/ROOT/pages/clustering/monitoring/show-servers-monitoring.adoc @@ -7,7 +7,7 @@ To monitor the state of individual servers in a cluster, use the `SHOW SERVERS` [[show-servers-monitoring-listing]] -== Listing Servers +== Showing servers *Syntax:* @@ -65,7 +65,7 @@ When running `SHOW SERVERS` against a cluster, expect similar output to the foll [[show-servers-monitoring-listing-extended]] -=== Listing more details of servers +=== Showing more details of servers If more details about the servers are needed, `SHOW SERVERS` can be appended with `YIELD *`. diff --git a/modules/ROOT/pages/clustering/multi-region-deployment/disaster-recovery.adoc b/modules/ROOT/pages/clustering/multi-region-deployment/disaster-recovery.adoc index fda7288ef5..5f6b700f73 100644 --- a/modules/ROOT/pages/clustering/multi-region-deployment/disaster-recovery.adoc +++ b/modules/ROOT/pages/clustering/multi-region-deployment/disaster-recovery.adoc @@ -206,8 +206,8 @@ Therefore, informing the cluster of servers which are lost is not enough. The databases hosted on lost servers also need to be moved onto available servers in the cluster, before the lost servers can be removed. ==== Verifying the state -The cluster's view of servers can be seen by listing the servers. -See xref:clustering/servers.adoc#_listing_servers[Listing servers] for more information. +The cluster's view of servers can be seen by showing the servers. +See xref:clustering/servers.adoc#_showing_servers[Showing servers] for more information. The state has been verified if *all* servers show `health` = `Available` and `status` = `Enabled`. [source, cypher] @@ -234,7 +234,7 @@ It was done in the < Deallocate databases]. @@ -183,7 +183,7 @@ To allow the same physical hardware to rejoin the cluster, reset the Neo4j insta This process ensures a new server ID is generated when the server starts again. ==== -== Listing servers +== Showing servers The Cypher command `SHOW SERVERS` displays all current servers running in the cluster, including servers yet to be enabled (i.e. servers in the _free_ state) in the DBMS as well as dropped servers. @@ -359,7 +359,7 @@ neo4j@system> ENABLE SERVER '25a7efc7-d063-44b8-bdee-f23357f89f01' OPTIONS {modeConstraint:'PRIMARY', allowedDatabases:['foo'], tags:['eu','eu-west']}; ---- + -* `modeConstraint` is used to control whether a server can only host standard databases in primary mode, only in secondary mode, or can host databases in either mode. +* `modeConstraint` is used to control whether a server can only host standard databases in primary mode, only in secondary mode, or can host databases in either mode. * `allowedDatabases` and `deniedDatabases` are collections of database names that filter which databases may be hosted on a server. The `allowedDatabases` and `deniedDatabases` are mutually exclusive and if both are specified, an error is returned. `allowedDatabases` and `deniedDatabases` do not affect composite databases, they are always available everywhere. @@ -388,7 +388,7 @@ Once enabled, a server does not automatically host databases unless: * New databases are created. * Existing database topologies are altered to request more hosts. * Another server is transitioned to the _deallocating_ state. -* You explicitly rebalance the databases across the cluster, possibly reallocating databases some to the newly added server(s). +* You explicitly rebalance the databases across the cluster, possibly reallocating databases some to the newly added server(s). [[removing-servers]] diff --git a/modules/ROOT/pages/configuration/neo4j-conf.adoc b/modules/ROOT/pages/configuration/neo4j-conf.adoc index 5c40ddcd75..5cf417b0b6 100644 --- a/modules/ROOT/pages/configuration/neo4j-conf.adoc +++ b/modules/ROOT/pages/configuration/neo4j-conf.adoc @@ -180,7 +180,7 @@ Disable this flag if you use embedded mode or have extensions or dependencies th [[neo4j-conf-current-settings]] -=== List currently active settings +=== Show currently active settings You can use `SHOW SETTINGS` to list the currently active configuration settings and their values. diff --git a/modules/ROOT/pages/configuration/ports.adoc b/modules/ROOT/pages/configuration/ports.adoc index ba1186baa1..ed68a2cb53 100644 --- a/modules/ROOT/pages/configuration/ports.adoc +++ b/modules/ROOT/pages/configuration/ports.adoc @@ -12,7 +12,7 @@ Specific recommendations on port openings cannot be made, as the firewall config When exposing network services, make sure they are always protected. ==== -== Listen address configuration settings +== Showen address configuration settings The listen address configuration settings will set the network interface and port to listen on. For example, the IP-address `127.0.0.1` and port `7687` can be set with the value `127.0.0.1:7687`. diff --git a/modules/ROOT/pages/configuration/show-settings.adoc b/modules/ROOT/pages/configuration/show-settings.adoc index 8223ca0266..404a0facee 100644 --- a/modules/ROOT/pages/configuration/show-settings.adoc +++ b/modules/ROOT/pages/configuration/show-settings.adoc @@ -1,9 +1,9 @@ :description: Information about the `SHOW SETTINGS` command. -:keywords: SHOW SETTINGS, configuration settings, listing settings +:keywords: SHOW SETTINGS, configuration settings, listing settings, showing settings :page-role: not-on-aura = Show configuration settings -This page describes listing configuration settings using the `SHOW SETTINGS` command. +This page describes showing configuration settings using the `SHOW SETTINGS` command. For general information about the `SHOW` command, see the link:{neo4j-docs-base-uri}/cypher-manual/current/clauses/show/[Cypher Manual -> SHOW]. [NOTE] @@ -12,7 +12,7 @@ For general information about the `SHOW` command, see the link:{neo4j-docs-base- To retrieve settings on a specific server, you need to directly connect to it using `bolt` scheme. For more information, see the link:{neo4j-docs-base-uri}/bolt/current/bolt[Bolt protocol documentation]. -* Configurations settings can also be listed using the xref:procedures/built-in-procedures.adoc#procedure_dbms_listConfig[`dbms.listConfig()`] procedure. +* Configurations settings can also be shown using the xref:procedures/built-in-procedures.adoc#procedure_dbms_listConfig[`dbms.listConfig()`] procedure. ==== [[syntax]] @@ -108,28 +108,28 @@ For dynamically updating a setting value, see link:{neo4j-docs-base-uri}/operati [[examples]] == Examples -The following examples show how to use the `SHOW SETTINGS` command to list configuration settings. +The following examples show how to use the `SHOW SETTINGS` command to show configuration settings. -=== List all settings with default return columns +=== Show all settings with default return columns [source, cypher] ---- SHOW SETTINGS ---- -=== List all settings with all return columns +=== Show all settings with all return columns [source, cypher] ---- SHOW SETTINGS YIELD * ---- -=== List all settings with specified return columns +=== Show all settings with specified return columns [source, cypher] ---- SHOW SETTINGS YIELD name, defaultValue, startupValue ---- -=== List named settings +=== Show named settings [source, cypher] ---- SHOW SETTINGS "server.bolt.enabled", "server.bolt.advertised_address", "server.bolt.listen_address" diff --git a/modules/ROOT/pages/database-administration/aliases/manage-aliases-composite-databases.adoc b/modules/ROOT/pages/database-administration/aliases/manage-aliases-composite-databases.adoc index 418b3cdec3..1f611a8e24 100644 --- a/modules/ROOT/pages/database-administration/aliases/manage-aliases-composite-databases.adoc +++ b/modules/ROOT/pages/database-administration/aliases/manage-aliases-composite-databases.adoc @@ -26,7 +26,7 @@ Local aliases always get the Cypher version of their target database and aliases ==== [[manage-aliases-composite-databases-list]] -== List database aliases in composite databases +== Show database aliases in composite databases Available database aliases in composite databases can be seen using `SHOW ALIASES FOR DATABASE`. The name of the composite database a particular database alias appears in the returned `composite` column. diff --git a/modules/ROOT/pages/database-administration/aliases/manage-aliases-standard-databases.adoc b/modules/ROOT/pages/database-administration/aliases/manage-aliases-standard-databases.adoc index f351400c47..62b876c084 100644 --- a/modules/ROOT/pages/database-administration/aliases/manage-aliases-standard-databases.adoc +++ b/modules/ROOT/pages/database-administration/aliases/manage-aliases-standard-databases.adoc @@ -47,7 +47,7 @@ This page describes managing database aliases for standard databases. For aliases created as part of a xref:scalability/composite-databases/concepts.adoc[composite database], see xref:database-administration/aliases/manage-aliases-composite-databases.adoc[]. [[manage-aliases-list]] -== List database aliases +== Show database aliases //// [source, cypher, role=test-setup] @@ -72,7 +72,7 @@ DEFAULT LANGUAGE CYPHER 25; ---- //// -You can list all available database aliases using the `SHOW ALIASES FOR DATABASE` command. +You can show all available database aliases using the `SHOW ALIASES FOR DATABASE` command. The command returns a table of all database aliases, whether they belong to a composite database or not. + If you need more details, you can append the command with `YIELD *`. The `YIELD *` clause returns the full set of columns. @@ -150,7 +150,7 @@ label:new[Introduced in 2025.06] The default language for non-constituent remote === Show all database aliases -To list all database aliases, use the `SHOW ALIASES FOR DATABASE` command without any additional parameters. +To show all database aliases, use the `SHOW ALIASES FOR DATABASE` command without any additional parameters. This command returns all database aliases, including local and remote aliases, for all databases in the DBMS. .Query @@ -173,7 +173,7 @@ SHOW ALIASES FOR DATABASE === Show a specific database alias -To list just one database alias, the `SHOW ALIASES` command takes an alias name: +To show just one database alias, the `SHOW ALIASES` command takes an alias name: .Query [source, cypher] diff --git a/modules/ROOT/pages/database-administration/standard-databases/listing-databases.adoc b/modules/ROOT/pages/database-administration/standard-databases/listing-databases.adoc index 9336e10397..9f9e73ab41 100644 --- a/modules/ROOT/pages/database-administration/standard-databases/listing-databases.adoc +++ b/modules/ROOT/pages/database-administration/standard-databases/listing-databases.adoc @@ -1,8 +1,8 @@ :description: how to list databases in Neo4j, use SHOW DATABASES command, see all available databases, databases states. How to filter listed databases in Neo4j. :page-role: enterprise-edition -= List databases += Show databases -You can list your databases using the Cypher command `SHOW DATABASES`. +You can show your databases using the Cypher command `SHOW DATABASES`. == Syntax @@ -36,7 +36,7 @@ If the `SHOW DATABASES` is combined with other clauses, the automatic re-routing == `SHOW DATABASES` output -Depending on what you want to see, you can list: +Depending on what you want to see, you can show different sets of databases: * All databases. * A particular database. diff --git a/modules/ROOT/pages/introduction.adoc b/modules/ROOT/pages/introduction.adoc index e3a1d9ce99..dc15528467 100644 --- a/modules/ROOT/pages/introduction.adoc +++ b/modules/ROOT/pages/introduction.adoc @@ -132,7 +132,7 @@ a| link:https://neo4j.com/docs/cdc/current/[Change Data Capture (CDC)] | {check-mark} | {check-mark} -| xref:monitoring/query-management.adoc[Listing and terminating running queries] +| xref:monitoring/query-management.adoc[Showing and terminating running queries] | {check-mark} | {check-mark} | {check-mark} diff --git a/modules/ROOT/pages/monitoring/background-jobs.adoc b/modules/ROOT/pages/monitoring/background-jobs.adoc index 40ecacb4cf..b4a1ba4495 100644 --- a/modules/ROOT/pages/monitoring/background-jobs.adoc +++ b/modules/ROOT/pages/monitoring/background-jobs.adoc @@ -23,7 +23,7 @@ Additionally, it should be noted that a single periodic job can contribute multi [[background-jobs-active]] -== Listing active background jobs +== Showing active background jobs An xref:authentication-authorization/index.adoc#auth-terminology[administrator] can list background jobs active on an instance: @@ -107,7 +107,7 @@ If a job supports reposting its progress, the progress will be reported in this [[background-jobs-failed]] -== Listing failed job executions +== Showing failed job executions An xref:authentication-authorization/index.adoc#auth-terminology[administrator] can list job executions failed on an instance: diff --git a/modules/ROOT/pages/monitoring/connection-management.adoc b/modules/ROOT/pages/monitoring/connection-management.adoc index a39fa510aa..24672bdc44 100644 --- a/modules/ROOT/pages/monitoring/connection-management.adoc +++ b/modules/ROOT/pages/monitoring/connection-management.adoc @@ -3,12 +3,12 @@ = Manage connections [[connection-management-list-connections]] -== List all network connections +== Show all network connections An xref:authentication-authorization/index.adoc#auth-terminology[administrator] is able to view all network connections within the database instance. Alternatively, the xref:authentication-authorization/index.adoc#auth-terminology[current user] may view all of their own network connections. -The procedure `dbms.listConnections` lists all accepted network connections for all configured connectors, including Bolt, HTTP, and HTTPS. +The procedure `dbms.listConnections` shows all accepted network connections for all configured connectors, including Bolt, HTTP, and HTTPS. Some listed connections might never perform authentication. For example, HTTP GET requests to the Neo4j Browser endpoint fetches static resources and does not need to authenticate. However, connections made using Neo4j Browser require the user to provide credentials and perform authentication. diff --git a/modules/ROOT/pages/monitoring/query-management.adoc b/modules/ROOT/pages/monitoring/query-management.adoc index 880a6b3919..c9f42ab933 100644 --- a/modules/ROOT/pages/monitoring/query-management.adoc +++ b/modules/ROOT/pages/monitoring/query-management.adoc @@ -4,7 +4,7 @@ = Manage queries [[query-management-list-queries]] -== List all running queries +== Show all running queries The procedure for listing queries, `dbms.listQueries()`, is replaced by the command for listing transactions, `SHOW TRANSACTIONS`. This command returns information about the currently executing query in the transaction. diff --git a/modules/ROOT/pages/performance/index-configuration.adoc b/modules/ROOT/pages/performance/index-configuration.adoc index 4a7955d26b..a24962e850 100644 --- a/modules/ROOT/pages/performance/index-configuration.adoc +++ b/modules/ROOT/pages/performance/index-configuration.adoc @@ -136,7 +136,7 @@ A full description of how to create and use full-text indexes is provided in the === Configuring a full-text index The following options are available for configuring full-text indexes. -For a complete list of Neo4j procedures, see xref:procedures/built-in-procedures.adoc#_index_management[Procedures]. +For a complete list of Neo4j procedures, see xref:procedures/built-in-procedures.adoc#_index_management[Built-in procedures]. `db.index.fulltext.default_analyzer`:: The name of the default analyzer when creating a new Full-text index. diff --git a/modules/ROOT/pages/procedures/built-in-procedures.adoc b/modules/ROOT/pages/procedures/built-in-procedures.adoc index 2b18610aea..f716593fea 100644 --- a/modules/ROOT/pages/procedures/built-in-procedures.adoc +++ b/modules/ROOT/pages/procedures/built-in-procedures.adoc @@ -25,7 +25,7 @@ This page provides a complete reference to Neo4j's built-in procedures. // * <<#_statistics_and_query_planning,Statistics and query planning>> // * <<#_transaction_management,Transaction management>> -For lists of changed, deprecated, or removed procedures in the 2025-2026 series, refer to xref:changes-2025-2026.adoc[Changes in Neo4j 2025-2026 series], xref:deprecations.adoc[Current deprecations], and xref:breaking-changes.adoc[Breaking changes in Neo4j 2025.01]. +For changed, deprecated, or removed procedures in the 2025-2026 series, refer to xref:changes-2025-2026.adoc[Changes in Neo4j 2025-2026 series], xref:deprecations.adoc[Current deprecations], and xref:breaking-changes.adoc[Breaking changes in Neo4j 2025.01]. The available procedures on a server depends on several factors: diff --git a/modules/ROOT/pages/procedures/call-procedures.adoc b/modules/ROOT/pages/procedures/call-procedures.adoc index 476022ae37..168cd3a85d 100644 --- a/modules/ROOT/pages/procedures/call-procedures.adoc +++ b/modules/ROOT/pages/procedures/call-procedures.adoc @@ -39,7 +39,7 @@ A Cypher statement made up of only a single `CALL` clause is known as a standalo === Call a procedure without arguments -This example calls the built-in procedure xref:procedures/built-in-procedures.adoc#procedure_db_labels[`db.labels()`], which lists all labels used in the database. +This example calls the built-in procedure xref:procedures/built-in-procedures.adoc#procedure_db_labels[`db.labels()`], which shows all labels used in the database. .Procedure call [source, cypher] diff --git a/modules/ROOT/pages/scalability/composite-databases/list-composite-databases.adoc b/modules/ROOT/pages/scalability/composite-databases/list-composite-databases.adoc index dfdd20fbba..1d3d43e509 100644 --- a/modules/ROOT/pages/scalability/composite-databases/list-composite-databases.adoc +++ b/modules/ROOT/pages/scalability/composite-databases/list-composite-databases.adoc @@ -1,7 +1,7 @@ :description: This page describes how to list composite databases. :page-role: enterprise-edition not-on-aura [[composite-databases-list]] -= List composite databases += Show composite databases //// [source, cypher, role=test-setup] @@ -12,7 +12,7 @@ CYPHER 25 CREATE ALIAS `library.sci-fi` FOR DATABASE `sci-fi`; ---- //// -You can list composite databases using the command `SHOW DATABASES`. +You can show composite databases using the command `SHOW DATABASES`. Composite databases are listed with the type `composite` in the `type` column of the result set. .Query diff --git a/modules/ROOT/pages/scalability/composite-databases/querying-composite-databases.adoc b/modules/ROOT/pages/scalability/composite-databases/querying-composite-databases.adoc index 9236845880..5741f49b20 100644 --- a/modules/ROOT/pages/scalability/composite-databases/querying-composite-databases.adoc +++ b/modules/ROOT/pages/scalability/composite-databases/querying-composite-databases.adoc @@ -152,7 +152,7 @@ The `CALL {}` sub-query executes once per input row. In this case, once selecting `cineasts.latest`, and once selecting `cineasts.upcoming`. [[composite-databases-queries-listing-graphs]] -=== Listing graphs +=== Showing graphs The built-in function link:{neo4j-docs-base-uri}/cypher-manual/current/functions/#header-query-functions-graph[`graph.names()`] returns a list containing the names of all constituent graphs on the current Composite database. diff --git a/modules/ROOT/pages/scalability/sharded-property-databases/listing-sharded-databases.adoc b/modules/ROOT/pages/scalability/sharded-property-databases/listing-sharded-databases.adoc index 60dc5b6505..4df9d2c0df 100644 --- a/modules/ROOT/pages/scalability/sharded-property-databases/listing-sharded-databases.adoc +++ b/modules/ROOT/pages/scalability/sharded-property-databases/listing-sharded-databases.adoc @@ -1,6 +1,6 @@ :page-role: new-2025.12 infinigraph not-on-aura :description: Listing sharded property databases -= Listing sharded property databases += Showing sharded property databases You can view all or a specific sharded property database using the `SHOW DATABASES` command. For details on the command syntax, arguments, and a complete list of the returned columns, see xref:database-administration/standard-databases/listing-databases.adoc[List databases]. @@ -14,7 +14,7 @@ If you have `CREATE/DROP/ALTER DATABASE`, `SET DATABASE ACCESS`, or `DATABASE MA If you lack any of these privileges, you will only be able to see the virtual sharded database. -== Listing virtual sharded databases +== Showing virtual sharded databases The virtual sharded database aggregates the information of the underlying shards. Some columns are empty for the virtual sharded database. @@ -66,7 +66,7 @@ a| The `currentStatus` is aggregated from the current status of the underlying s | |=== -== Listing graph shards +== Showing graph shards The following columns are specific to graph shards in a sharded property database: @@ -96,7 +96,7 @@ The lag is expressed in negative integers. | |=== -== Listing property shards +== Showing property shards The following columns are specific to property shards in a sharded property database: From 519538ead53ebe2d6a19038c469f21c838a0a862 Mon Sep 17 00:00:00 2001 From: Reneta Popova Date: Wed, 27 May 2026 14:21:30 +0100 Subject: [PATCH 2/5] Update modules/ROOT/pages/monitoring/query-management.adoc Co-authored-by: Natalia Ivakina <82437520+NataliaIvakina@users.noreply.github.com> --- modules/ROOT/pages/monitoring/query-management.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/ROOT/pages/monitoring/query-management.adoc b/modules/ROOT/pages/monitoring/query-management.adoc index c9f42ab933..f48ea6d64f 100644 --- a/modules/ROOT/pages/monitoring/query-management.adoc +++ b/modules/ROOT/pages/monitoring/query-management.adoc @@ -8,7 +8,7 @@ The procedure for listing queries, `dbms.listQueries()`, is replaced by the command for listing transactions, `SHOW TRANSACTIONS`. This command returns information about the currently executing query in the transaction. -For more information on the command, see the link:{neo4j-docs-base-uri}/cypher-manual/current/clauses/transaction-clauses#query-listing-transactions[Cypher manual -> `SHOW TRANSACTIONS` command]. +For more information on the command, see the xref:database-internals/show-and-terminate-transactions.adoc#show-transactions[Database internals -> Show and terminate transactions]. [[query-management-terminate-queries]] == Terminate queries From 0e13892f32a16939e23bea38a0ed59d67225399b Mon Sep 17 00:00:00 2001 From: Reneta Popova Date: Wed, 27 May 2026 14:24:15 +0100 Subject: [PATCH 3/5] Apply suggestion from @NataliaIvakina Co-authored-by: Natalia Ivakina <82437520+NataliaIvakina@users.noreply.github.com> --- modules/ROOT/pages/configuration/ports.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/ROOT/pages/configuration/ports.adoc b/modules/ROOT/pages/configuration/ports.adoc index ed68a2cb53..ba1186baa1 100644 --- a/modules/ROOT/pages/configuration/ports.adoc +++ b/modules/ROOT/pages/configuration/ports.adoc @@ -12,7 +12,7 @@ Specific recommendations on port openings cannot be made, as the firewall config When exposing network services, make sure they are always protected. ==== -== Showen address configuration settings +== Listen address configuration settings The listen address configuration settings will set the network interface and port to listen on. For example, the IP-address `127.0.0.1` and port `7687` can be set with the value `127.0.0.1:7687`. From 57003266901a7ea6d2b773cfbfab87b8499714e8 Mon Sep 17 00:00:00 2001 From: Reneta Popova Date: Wed, 27 May 2026 14:25:25 +0100 Subject: [PATCH 4/5] Apply suggestion from @renetapopova --- modules/ROOT/pages/procedures/call-procedures.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/ROOT/pages/procedures/call-procedures.adoc b/modules/ROOT/pages/procedures/call-procedures.adoc index 168cd3a85d..476022ae37 100644 --- a/modules/ROOT/pages/procedures/call-procedures.adoc +++ b/modules/ROOT/pages/procedures/call-procedures.adoc @@ -39,7 +39,7 @@ A Cypher statement made up of only a single `CALL` clause is known as a standalo === Call a procedure without arguments -This example calls the built-in procedure xref:procedures/built-in-procedures.adoc#procedure_db_labels[`db.labels()`], which shows all labels used in the database. +This example calls the built-in procedure xref:procedures/built-in-procedures.adoc#procedure_db_labels[`db.labels()`], which lists all labels used in the database. .Procedure call [source, cypher] From 18880d8906b9dfe6d84cda1e23e7f691c234ea92 Mon Sep 17 00:00:00 2001 From: Reneta Popova Date: Wed, 27 May 2026 14:28:31 +0100 Subject: [PATCH 5/5] Apply suggestion from @renetapopova --- .../composite-databases/querying-composite-databases.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/ROOT/pages/scalability/composite-databases/querying-composite-databases.adoc b/modules/ROOT/pages/scalability/composite-databases/querying-composite-databases.adoc index 5741f49b20..9236845880 100644 --- a/modules/ROOT/pages/scalability/composite-databases/querying-composite-databases.adoc +++ b/modules/ROOT/pages/scalability/composite-databases/querying-composite-databases.adoc @@ -152,7 +152,7 @@ The `CALL {}` sub-query executes once per input row. In this case, once selecting `cineasts.latest`, and once selecting `cineasts.upcoming`. [[composite-databases-queries-listing-graphs]] -=== Showing graphs +=== Listing graphs The built-in function link:{neo4j-docs-base-uri}/cypher-manual/current/functions/#header-query-functions-graph[`graph.names()`] returns a list containing the names of all constituent graphs on the current Composite database.