Storing a serialized array in the database an anti pattern? Rails

Question

As specified in this other question you can store serialized data in the database. What i want to know is if i really should or just create a simple extra table.

Object has a list of asociated numbers.

Will probably need to check if an object has a particular number.

Will never update it.

Wont query it.

Have property numbers as serialize?

Have table Numbers belonging to Objects?

BTW im using rails 5.1 and postgresql.

Thanks

mu is too short · Accepted Answer · 2017-08-19 16:50:43Z

2

Since you're using PostgreSQL, you actually have a third option: use an array column.

Add the array: true option when creating the column:

t.integer :column_name, array: true

and then model.column_name will be a Ruby array and you can use all the PostgreSQL array operators and functions to work with and query the array.

I tend to think that you're usually better off with a separate table but an array column is often convenient and fairly easy to unroll into a separate table if necessary.

I'd stay away from serialize. That throws a blob of YAML into your database and YAML is difficult and cumbersome to query let alone manipulate inside the database.

answered Aug 19, 2017 at 16:50

mu is too short

436k71 gold badges863 silver badges822 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Cary Swoveland Over a year ago

Yes, accidental submit. Thanks. I deleted my answer and will delete this comment as well.

Collectives™ on Stack Overflow

Storing a serialized array in the database an anti pattern? Rails

1 Answer 1

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related