Question

I’m working on a PHP app which requires various settings to be stored in a database. The client often asks if certain things can be added or changed/removed, which has been causing problems with the table design. Basically, I had a lot of boolean fields which simply indicated if various settings were enabled for a particular record.

In order to avoid messing around with the table any more, I’m considering storing the data as a serialized array. I have read that this is considered bad practice, but I think this is a justified case for using such an approach.

Is there any real reason to avoid doing this?

Any advice appreciated.

Thanks.

Answer 1

The real reason is normalisation, and you will break the first normalform by doing it.

However, there are many cases in which a breach of the normal forms could be considered. How many fields are you dealing with and are they all booleans?

Storing an array serialized as a string in your database will have the following disadvantages (among others):

• When you need to update your settings you must first extract the current settings from the database, unserialize the array, change the array, serialize the array and update the data in the table.
• When searching, you will not be able to just ask the database whether a given user (or a set of users) has a given setting disabled or enabled, thus you won’t have any chances of searching.

Instead, you should really consider the option of creating another table with the records you need as a one-to-many relation from your other table. Thus you won’t have 30 empty fields, but instead you can just have a row for each option that deviates from the default (note that this option has some disadvantages aswell, for example if you change the default).

In sum: I think you should avoid serializing arrays and putting them into the databases, at least if you care just a tiny bit about the aforementioned disadvantages.