Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

information_schema and other metadata queries aren't correct #20

Closed
OllieJones opened this issue Mar 4, 2023 · 3 comments
Closed

information_schema and other metadata queries aren't correct #20

OllieJones opened this issue Mar 4, 2023 · 3 comments
Assignees
Labels
bug Something isn't working enhancement New feature or request

Comments

@OllieJones
Copy link
Contributor

The information_schema and metadata queries need work. Many! plugins use them, https://wpdirectory.net/search/01GTQD2377VCEWY8WHAMK8PC0K

Testing criteria: at least the top 20 plugins using the information_schema work properly. (Excluding site-clone, backup, caching, etc).

@OllieJones OllieJones added bug Something isn't working enhancement New feature or request labels Mar 4, 2023
@OllieJones OllieJones self-assigned this Mar 4, 2023
@OllieJones
Copy link
Contributor Author

@aristath I hope you don't mind me working on this kind of compatibility-layer code. If so, just tell me and I'll step back,

Is this the right repo to contain this work? I'm not sure what your plan for the monorepo is.

It seems wise to think through what this rewriter will look like when it has 20 or more query-editing rules. For the ecosystem (plugin and template authors) it will be really helpful to have a filter-oriented framework they can field-extend if they need to.

Some of the necessary rewrites are doable with your lex / parse scheme. Others (information_schema) are going to require parsing the query and figuring out how to get the required data another way. Finally, there are queries that depend on dialect-specific features, like the query used to delete expired transients.

@aristath
Copy link
Member

aristath commented Mar 7, 2023

@aristath I hope you don't mind me working on this kind of compatibility-layer code. If so, just tell me and I'll step back,

Of course I don't mind... The more the merrier, and I value your input tremendously! 👍

Is this the right repo to contain this work? I'm not sure what your plan for the monorepo is.

For the time being, this is the right repo, yes.
The plan is to move this back to the monorepo (see WordPress/performance#661), but that will take a few weeks, as we first need to complete all the infrastructure necessary to deploy plugins etc from there.
Until that happens, we can use this repo for all development, and then we'll be porting the code in the PL monorepo when the time comes

@OllieJones
Copy link
Contributor Author

Advanced Database Cleaner doesn't yet clean expired transients.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants