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
Setup a nextcloud with a PG database, and a DBName that contains a dot in its name
Access the serverInfo app
Expected behaviour
The server info page should display
Actual behaviour
An error is reported, with this message in the logs:
Trying to access array offset on value of type bool at /var/www/html/apps/serverinfo/lib/DatabaseStatistics.php#132
Quick analysis
See lib/DatabaseStatistics.php#L123
There is a split of the DB name on a . separator.
Due to this, with my DB name of cloud.mydomain.fr, the next query will be
SELECT oid FROM pg_database WHERE datname = 'cloud'
instead of being
SELECT oid FROM pg_database WHERE datname = 'cloud.mydomain.fr'
This looks like a bug, since dbName with dots seems to be supported by the rest of nextCloud (all other features are working as expected)
I remember a bug report about database names with dots in nextcloud/server, but were unable to find it again.
Is the database size important for anyone?
Steps to reproduce
Expected behaviour
The server info page should display
Actual behaviour
An error is reported, with this message in the logs:
Quick analysis
See lib/DatabaseStatistics.php#L123
There is a split of the DB name on a
.
separator.Due to this, with my DB name of
cloud.mydomain.fr
, the next query will beinstead of being
This looks like a bug, since dbName with dots seems to be supported by the rest of nextCloud (all other features are working as expected)
Server configuration
Operating system:
Nexcloud docker image nextcloud:27-apache
Web server:
Nexcloud docker image nextcloud:27-apache
Database:
PostgreSQL 16
PHP version:
Nexcloud docker image nextcloud:27-apache
Nextcloud version: (see Nextcloud admin page)
27.1.5
Where did you install Nextcloud from:
Nexcloud docker image nextcloud:27-apache
Nextcloud configuration:
Logs
The text was updated successfully, but these errors were encountered: