Title: Separate DB table &#8211; why?
Last modified: March 10, 2017

---

# Separate DB table – why?

 *  Resolved [Nazar Hotsa](https://wordpress.org/support/users/bugnumber9/)
 * (@bugnumber9)
 * [9 years, 3 months ago](https://wordpress.org/support/topic/separate-db-table-why/)
 * Hiya Harry,
 * I was wondering why do you use a separate DB table (wp_harrys_gravatar_cache)
   to store plugin options? Isn’t this an overkill for storing a single record with
   10 values?
    I’d say a single entry in wp_options table with serialized data makes
   more sense, doesn’t it?
 * Thanks.

Viewing 1 replies (of 1 total)

 *  Plugin Author [Harry Milatz](https://wordpress.org/support/users/harry-milatz/)
 * (@harry-milatz)
 * [9 years, 3 months ago](https://wordpress.org/support/topic/separate-db-table-why/#post-8898478)
 * Hi,
 * no, that isn’t an overkill;) There is not really a difference (in loading time)
   getting the values from wp_options or from the own table. And in case of deinstallation
   these options/the table is deleted without touching the wp_options table.
 * Best regards,
    Harry

Viewing 1 replies (of 1 total)

The topic ‘Separate DB table – why?’ is closed to new replies.

 * ![](https://ps.w.org/harrys-gravatar-cache/assets/icon-256x256.png?rev=1495314)
 * [Harrys Gravatar Cache](https://wordpress.org/plugins/harrys-gravatar-cache/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/harrys-gravatar-cache/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/harrys-gravatar-cache/)
 * [Active Topics](https://wordpress.org/support/plugin/harrys-gravatar-cache/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/harrys-gravatar-cache/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/harrys-gravatar-cache/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [Harry Milatz](https://wordpress.org/support/users/harry-milatz/)
 * Last activity: [9 years, 3 months ago](https://wordpress.org/support/topic/separate-db-table-why/#post-8898478)
 * Status: resolved