Separate DB table – why?

  • Resolved Nazar Hotsa

    (@bugnumber9)


    7 years, 12 months ago

    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

    (@harry-milatz)

    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.