Extension Development - Use existing settings column or create a new table?

Question

I was pondering this today and trying to decide on the best route when it comes to storing data for an extension.

The data I am storing in an extension involves a many to many relationship with two entities.

When do you use the settings column in exp_extensions versus creating your own table where the data isn't serialized?

Let's say I have multiple instances, but with each single instance there will be the need to update data, delete, and relate to a member group id in the extension settings view.

One route I thought of is to unserialize the data, update the array, and then update the db? Yet with a table, you can utilize CI's active record functionality with data that is stored nicely. I'm confused on when to use one over the other. Help?

Answer 1

In this case, I think building your own settings table is the way to go for sure. Using the settings column should really only be for very minor yes/no types of settings, not storing actual data. Especially when you get into supporting MSM, where you need settings for each site, it can get hairy fast.

Plus, then your data is more easily searchable and readable, and you can be more selective about what you need to SELECT at any given time, etc, etc.

So yes: your own DB table.