Sure, why not? But what do you mean by “non-WordPress”? Is it a table to be used by something custom on your site? If not, if it’s used by some other web app, then it should be in its own database, with a different db user, for security reasons.
Viewing 1 replies (of 1 total)
The topic ‘non-wordpress table’ is closed to new replies.
