WordPress Development Stack Exchange is a question and answer site for WordPress developers and administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have an application built in asp.net but i'd like to port it over to wordpress as a plugin. Is it practical to develop the php version of this app using the Wordpress options table or should i rather create new database tables in the existing wordpress database?

Lastly this next question may be answered by answering the first question hopefully and that is: When should I use wordpress option tables over creating the database tables for the intended plugin?

Thanks way in advance..

share|improve this question

migrated from stackoverflow.com May 25 '12 at 23:55

This question came from our site for professional and enthusiast programmers.

Welcome to SO. What does this application do? – FelipeAls May 25 '12 at 21:05

Generally speaking, it's better to use the WordPress options table unless you have an enormous amount of data.

If you also use the WordPress Options API you can easily store your options grouped into 1 or several serialized arrays. WordPress handles the serialization of the data and by default options are set to autoload and cached so you save on any additional queries.

You also have the benefit of using built in functions like get_option(), update_option(), etc...

share|improve this answer

As an efficiency issue it's faster to use separate database tables and to join them with the wordpress tables.

That will mean writing alot of code using the wordpress pluggin api if you want to be rigurous.

If it's not that complicated / data-intensive you could use the options and save yourself some trouble.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.