News for hackers. Stuff that matters.
Re:When to Avoid JSONB in a PostgreSQL Schema by strommen on Friday September 02, 2016 @12:18AM (#12410808)
EAV is an anti-pattern?

If you don't have JSONB, EAV is the only remotely-reasonable way to implement user-defined fields (e.g. product-specific attributes in e-commerce).

Re:When to Avoid JSONB in a PostgreSQL Schema by malisper on Friday September 02, 2016 @01:03AM (#12410961)
If you want to allow user-defined fields in a relational database, your realistic are either EAV or stuff json into a text column. EAV, if done extremely carefully, can be a good solution, but 99% of the time, it's going to be a huge pain.
Re:When to Avoid JSONB in a PostgreSQL Schema by approachingtraj on Friday September 02, 2016 @05:47AM (#12411937)
> stuff json into a text column

You did see the article was about JSONB, which is significantly more sophisticated than "json in a text column", yes?

Re:When to Avoid JSONB in a PostgreSQL Schema by malisper on Friday September 02, 2016 @01:54PM (#12414843)
Yes, the person I was replying to was asking about what to do if you don't have jsonb.