On Tue, May 14, 2013 at 11:58 AM, Michael Bayer <mike...@zzzcomputing.com> wrote: > When you are storing data with key/values, where the set of keys is part of > the data. Storing configurational data is the main use case. HSTORE not > an option because it is postgresql-specific.
Configuration data can be json'd or pickled. You'd only use EAV if the set of keys or attributes is big enough that you can't json or pickle. -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at http://groups.google.com/group/sqlalchemy?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
