Try refactor wp db query --defaults
handling, fix #237
#285
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.
Try fix #237
Code change is all Copilot.
I reviewed it for general sanity, but I simply don't know enough
wp db
internals to know whether this direction is where we want to go.But I'll file this anyway to get movement and directional discussion going.
I feel like currently
wp db query
just doing--no-defaults
basically hard-coded is overly naive for many real world use cases, and needs to be refactored no matter what. If you can't even connect to remote SSL-secured databases, I'm not sure how we can ignore this in 2025.My Copilot strategy session can be reviewed at lkraav#2
EDIT I've now also tested it, and this PR does make at least
--defaults
and/or--ssl-verify-server-cert
work.