Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upSupport for storing CPT metadata in Custom Database Tables #3759
Milestone
Comments
This comment has been minimized.
This comment has been minimized.
You already can do this without the need for changes to Gutenberg. You can do it now without Gutenberg actually. We do it on projects of ours semi regulrly. |
This comment has been minimized.
This comment has been minimized.
@pmgarman Yes, you can already save the CPTs metadata in custom db tables without Gutenberg but I'm fairly certain that you can't yet do that with Gutenberg. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As an example, we have two CPTs, Books and Authors, and we would like to store the Books metadata (i.e parent_id, isbn, subtitle, average_rating, ratings_count, publication_date, num_pages, bisac_code, author_id, etc) in a custom DB table "Books" and also store the Authors metadata (i.e works_count, date_of_birth, fans_count, average_rating, etc) in a custom DB table "Authors".
We would then like to query the data like so:
Storing all the CPTs metadata in
wp_postmeta
is not an option because searching over 1 million rows would be very slow and doesn't scale and it's the reason why WooCommerce is moving orders and products to custom DB tables as well.Will I be able to add custom fields/meta blocks to the two CPTs in Gutenberg and then save that meta data in custom database tables?