Edit - WordPress Development Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

You don't understand nor the question, nor the problem with PW. [Firstly] wp_posts and wp_postmeta is the MOST garbage tables which world databases ever have. Especially when you have CPT with 100 CustomFields. Thus I'm trying to split them and store all additional CPT Metabox CustomFields not at wp_postmeta trash, but at separate custom table like "wp_Cars". [Secondly] For this CPT which CustomFields stored at custom table I need to store many Taxonomies Terms ID's. I have 2 options: A or B. I've asking of which is better and why?

user234970
– user234970

2023-08-22 14:59:56 +00:00
Commented Aug 22, 2023 at 14:59

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »