Ultimate Stupid Question On Data Structure

Assuming that I create say 50 custom fields for a listing and yes this could be extreme, and not really wanting to get in to why wp works the way it does…. some things just don’t make sense especially on the number of db querries that need to be made to get a listing.

Mark I know this concept will probably have you either laffing, ripping your hair out or saying hmmmm interesting idea.

Here we go:

create a new table call it say – listings

in the listings table you maintain all of the data regarding a particular listing, including all custom fields.

When creating a custom field it would be created in the listing table not as a reference in wp_post_meta

All the fields would be in this listing table as such db query would be much faster and you could key certain fields to speed things up.

You would then only reference the listing ID to a Post ID.

The reason for this concept is that trying to upload hundreds or even tens of thounds of listings is impossible, also your not having to deal with linkins in other tables w_term_relationships, w_term_taxonomy etc.

Tell me i’m crazy but a new table with all the data for a listing record is a simple import and 1 query, unlike how wp now handles things, if you have 50 custom fields plus what you have hard coded now a single listing can take 70 or more rows of data.

Thoughts anyone?