On Monday 14 Sep 2015 12:28:48 Jeremy Evans wrote: > In general, I don't > recommend the EAV approach used by rails-settings except as a last resort. > If you are using PostgreSQL, a jsonb/hstore column for storing settings is > a better approach.
Just out of curiosity, how would you use jsonb/hstore as alternative to EAV (i.e. something like a table with (entity, settings) columns?) and what advantages do you see in it over EAV? Asking as we're just in the process of redesigning some tables and we were actually thinking about splitting some flags and options into an EAV table, but I'm curious to see a better approach. -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sequel-talk. For more options, visit https://groups.google.com/d/optout.
