There are no product-specific tables in the database
-
However, they disrespectfully deleted my comment. And they gave the excuse that it was a support request and it wasn’t. It was just a comment, but I will write it differently as a comment again. Until this time, they have no excuse to delete it. This is not a proper global team approach. Your disrespect will not be forgotten.
one of the biggest weaknesses of this system is that there are no specific product tables in the database.
Everything is mixed and the products are stored among the default WordPress post types. Products are stored in the same posts and pages, and this is not true. It should not be like this.
This causes the speed to decrease and there is no direct and easy access to the tables. It also makes scalability or migration difficult.Also, if the users of this system have many products and posts on the site, they face a significant decrease in the loading speed of the site, they also do not have access to the tables, and everything becomes confusing and complicated. This makes it very difficult even when they want to write a dedicated plugin, or develop a plugin.
This wrong approach existed from the beginning and is still continuing, if this wrong path is not stopped, it will continue and make the work harder and harder every day. This is something that should be paid attention to.
I will give some examples. It needs separate dedicated tables like this.
wc_products wc_product_attributes wc_product_attribute_values wc_product_downloads wc_product_relationships wc_product_variation_attribute_values
This is a topic that WooCommerce developers know, but because of laziness and hard work; They run away from it with different excuses!
- The topic ‘There are no product-specific tables in the database’ is closed to new replies.