Show all DB Connections on Status Page

indeed. although not that popular in confusion, but the tuple (server, db_name) would be almost perfectly unique.

i'd appreciate to see that coming! Much better super admin usability.

I'm cool with it if someone wants to roll a patch.

I guess no one rolled a patch.

Here is a patch that will show one of the following messages on the Status Report,

If the database is using a default prefix:
Database connection information Host: "localhost", Database: "my_database", Prefix: "_myprefix"

If the database does not use a default prefix:
Database connection information Host: "localhost", Database: "my_database", no prefix

Best regards,
Nestor

Adding tags to the ticket.
This is a Costa Rican Team trying to fix as many tickets as possible today to contribute to the community.

Here is a screenshot of how this modification looks like:

Nestor

Has this been tested on SQLite or PostgreSQL yet? It looks fine to me from a MySQL perspective, but I don't think it will work for SQLite since it doesn't have a "host" key.

I will have to set up environments to test it, also if someone volunteers for testing it on those environments it would be great

This looks like a good novice issue

I rerolled the patch from #4. Git fixed it with an automerge (yay!). It removed a $ from before a t();

<        'title' => $t('Database system version'),
---
>        'title' => t('Database system version'),

I don't have SQLite or PostgreSQL. I tried drush quick-drupal, but my SQLite doesn't work. : (

Needs a reroll, and testing on other DBs.

• Moved up a few lines to agree with the alphabetical order displayed (in English).
• Added check for 'host' to work with sqlite\Connection.
• Removed double-quotes since the % placeholder substitution already gives <em> markup for the variable values.
• Split the variables into separate lines. (Using <br /> there, not sure if that is correct.)

I have only tested this with MySQL.

(Code) looks very nice for me.

Patch applied cleanly. Screenshots attached showing changes after patch and missing feature before patch is applied.

#8 points out that this needs postgres and sqlite testing - no one has provided any evidence of testing it on them.

Also atm this is classed as a feature - I really don't think it is - it's more a task but even with the re-classification I don't think it meets that beta evaluation criteria. See https://www.drupal.org/core/beta-changes for more.

No longer postponed.

Somehow the patch from 2014 no longer applies.

Re-rolled #16

Reroll looks good. Now we need an automated test.

Not sure about the test.

Looks good to me.
Testing has been added.
It is RTBC for me.
Nice to see that a Drupal 7 request made it.

StatusTest changes fails on SQLite: https://git.drupalcode.org/project/drupal/-/jobs/11024816

And not just that, there was an error in they the prefix was gathered. I also significantly changed the test.

Looks good to me.
Back to RTBC.

This is getting info for the default database connection, but the original feature request was for all database connections, should we be doing that? e.g. from https://api.drupal.org/api/drupal/core%21lib%21Drupal%21Core%21Database%...

his is getting info for the default database connection, but the original feature request was for all database connections, should we be doing that?

Yes, we should do that!

After I updated this for all connections I read this $databases['default']['replica'][] = $info_array; in settings.php. Unless that is incorrect, this needs to be updated to work with another level of nesting.

Looks good to me.
Back to RTBC.