Support for storing CPT metadata in Custom Database Tables #3759
Labels
[Feature] Block API
API that allows to express the block paradigm.
[Feature] Extensibility
The ability to extend blocks or the editing experience
Framework
Issues related to broader framework topics, especially as it relates to javascript
[Priority] Low
Used to indicate that the issue at hand isn't a top priority to address and can be handled later
[Type] Enhancement
A suggestion for improvement.
Milestone
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?
The text was updated successfully, but these errors were encountered: