Skip to content

Report the database driver name as database_engine instead of the connection name - #994

Merged
pushpak1300 merged 1 commit into
laravel:mainfrom
sulimanbenhalim:fix/application-info-database-engine
Sep 3, 2026
Merged

Report the database driver name as database_engine instead of the connection name#994
pushpak1300 merged 1 commit into
laravel:mainfrom
sulimanbenhalim:fix/application-info-database-engine

Conversation

@sulimanbenhalim

Copy link
Copy Markdown
Contributor

application-info returns config('database.default') as database_engine which is the connection name not the engine. they only match when the connection happens to be named after its driver, rename the default connection and the tool reports that name as the engine to every agent that calls it

tried it on a fresh app with the default connection named landlord (sqlite driver, spatie multitenancy style naming), on main application-info says "database_engine": "landlord" and with this change it says "sqlite"

DB::connection()->getDriverName() is what database-schema already uses for its engine field and database-connections already labels config('database.default') as default_connection so this just brings application-info in line. getDriverName() reads the driver off the config, it doesnt open a connection

re-file of #970, reviewed and re-tested individually

@pushpak1300
pushpak1300 merged commit f22c63d into laravel:main Sep 3, 2026
24 checks passed
@sulimanbenhalim
sulimanbenhalim deleted the fix/application-info-database-engine branch September 3, 2026 12:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants