Skip to content

Commit

Permalink
Document SHOW DATABASES fields that can be NULL (neo4j#1562)
Browse files Browse the repository at this point in the history
Some of the fields in SHOW DATABASES will always be null for databases
that are not running. Update the documentation to reflect this.
  • Loading branch information
mnd999 authored Apr 22, 2024
1 parent e964b60 commit 7b4d5c0
Showing 1 changed file with 11 additions and 0 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -35,6 +35,9 @@ A database may be described as read-only when using `ALTER DATABASE ... SET ACCE

| databaseID
| The database unique ID.

A database must be `online` or `deallocating` for this value to be available.
For other database states the value will be `NULL`.
| STRING

| serverID
Expand Down Expand Up @@ -137,16 +140,24 @@ The value is a string formatted as:
----
{storage engine}-{store format}-{major version}.{minor version}
----
A database must be `online` or `deallocating` for this value to be available.
For other database states the value will be `NULL`.
| STRING

| lastCommittedTxn
| The ID of the last transaction received.

A database must be `online` or `deallocating` for this value to be available.
For other database states the value will be `NULL`.
| INTEGER

| replicationLag
|
Number of transactions the current database is behind compared to the database on the primary instance.
The lag is expressed in negative integers. In standalone environments, the value is always `0`.

A database must be `online` or `deallocating` for this value to be available.
For other database states the value will be `NULL`.
| INTEGER

|constituents
Expand Down

0 comments on commit 7b4d5c0

Please sign in to comment.