[Bug]: Nextcloud 35.0.0 loses numeric dbdriveroptions keys

[eehakkin]

⚠️ This issue respects the following points: ⚠️

• This is not a troubleshooting question, general support matter, or webserver/proxy problem, but likely a bug (if unsure, ask the Community Help Forum).
• This issue is not already reported on Github OR solved at the Community Help Forum (I've searched!).
• I'm using a maintained major version of Nextcloud Server and tested against the latest patch level. (Supported major versions and current patch levels).
• I agree to follow Nextcloud's Code of Conduct.
• I've tried my best to provide clear reproduction steps that someone unfamiliar with this bug could use to reproduce it.

Bug description

MySQL dbdriveroptions (such as [\Pdo\Mysql::ATTR_SSL_CA => '/path/to/ca.crt'] are not passed correctly to a PDO driver because ConnectionFactory uses array_merge which does not retain numeric keys. In the end, the PDO driver receives [0 => '/path/to/ca.crt'].

Steps to reproduce

1. Configure explicit dbdriveroptions (such as 'dbdriveroptions' => [\Pdo\Mysql::ATTR_SSL_CA => '/path/to/ca.crt']) or implicit ones (such as 'dbtype' => 'mysql' with 'dbsslca' => '/path/to/ca.crt' where dbsslca is implicitly converted to dbdriveroptions).
2. Intercept the PDO driver options or use driver options which are mandatory for a MySQL connection.

Expected behavior

dbdriveroptions are passed correctly do the PDO driver.

Nextcloud Server version

35

Operating system

Debian/Ubuntu

PHP engine version

PHP 8.4

Web server

Apache (supported)

Database engine version

MariaDB

Is this bug present after an update or on a fresh install?

Upgraded to a MAJOR version (ex. 31 to 32)

Are you using the Nextcloud Server Encryption module?

Encryption is Disabled

What user-backends are you using?

• Default user-backend (database)
• LDAP/ Active Directory
• SSO - SAML
• Other

Configuration report

List of activated Apps

Nextcloud Signing status

Nextcloud Logs

Additional info

No response