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

feat: register table on plugin activation instead of check when DB class creates #3854

ravinderk opened this issue Nov 20, 2018 · 0 comments


None yet
1 participant
Copy link

commented Nov 20, 2018


Currently, every DB class calls register_table function when creating object ob that class which first do a SQL query to compare DB version, if we have the old version to DB then new table will install.


We can reduce up to 10 query on every page load by moving table register functionality to plugin activate:

Acceptance Criteria

  • Make table register process to the plugin activation
  • Get all DB version at once *_db_version for table version comparison (no need)
  • Table must install on single site on activation.
  • Table must install on subsite on activation of multisite.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.