i don't like devs who put serialized data into a relational database. guys, do you even know how to relational database? 😭😭😭

If application has parameters that do not appear in every record then its better than having extra NULLs everywhere. Although searching would be a bit handicapped. Everything has its ups and downs

@ArturS ofc, but i don't see any good point in storing serialized data in a mysql table :/

@bjoer751 thanks dude, haven't seen this yet. but sadly the serialized objects are just stored in string or blob columns :/
i wont get why someone has to use this, if someone really needs to save an object, then i'm not sure if this person understands the principles of relational databases 😞

Yeah, it didn't sit well with me at first either. But we've started doing this recently.

For us, it's always for data that will:
1) never be searched upon
2) and may change shape over time

Application settings is a prime example. And I can live with that.

@zourtney ok, seems legit.
i just thought this is an absolute no-go ^^
but it seems that it has some benefits in some situations :)