[12.x] Prioritize Current Schema When Resolving the Table Name in db:table
Command
#56646
+11
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
php artisan db:table
command ignores configured database and uses first alphabetical database #56393When running the
db:table
Artisan command with a non-schema-qualified table name (for example,db:table users
), the command currently searches for the table name in an alphabetically sorted list, causing the configured current schemas to be ignored.This PR updates the command to prioritize the current schema when resolving the table name. This ensures that the
db:table
command aligns with expected database search order rather than alphabetical schema sorting.search_path
config property first, then fall back to other schemas.