Database structure: Serialization everywhere?????
-
Dear developers,
so I do use WordPress because my boss like how it has good support for plugins and themes and how simple it is to work with it (for him), but guys, really? For Creator’s sake, storing list of active plugins in a serialized array in wp_options table??? Are you kidding me? The possibility to create tables with columns and rows in a database (do you understand that word?) isn’t there for you to laugh at it! I am one second from spilling every naughty word I know here!
Plusins list?
{plugin_identification, blah blah blha, active - boolean}
Plugin settings? Well, watch this:
{plugin_identification, setting_name, setting_value) with primary key (plugin_identification, setting_name}
You’re using serialization in absoluteny improper places, really, for me it seems like you needed something a looong time ago and you were too lazy to create a sensemaking database structure for it, so you just serialized it everything and now people who are solving broken upgrades can loose their mind.
Yours serialized,
Mind Blown Up
- The topic ‘Database structure: Serialization everywhere?????’ is closed to new replies.