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

#30262 Combine terms and term_taxonomy tables #8354

Draft
wants to merge 28 commits into
base: trunk
Choose a base branch
from

Conversation

johnbillion
Copy link
Member

This is some initial investigation into the feasibility of doing this. Thar be dragons.

Trac ticket: https://core.trac.wordpress.org/ticket/30262

Copy link

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

  • The Plugin and Theme Directories cannot be accessed within Playground.
  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

@spacedmonkey
Copy link
Member

I am very interested in being involved in this ticket. Please ping me for code review.

@johnbillion
Copy link
Member Author

Cheers Jonny, will do. I'm going to try an alternative approach (converting wp_terms to a view and retaining the wp_term_taxonomy table) and then we can evaluate the pros and cons of both and go from there.

@spacedmonkey
Copy link
Member

The approach of using a view has it's own problems. The biggest one to me is permissions. Do all database users have access to create a views? How will that work in Multisite?

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