SQLAlchemy has the ability to use a 'vertical' table structure to lay out what would essentially be an Entity-Attribute-Value backend. I was wondering if anyone had implemented this type of structure into a Turbogears application or even just a hypothetical example?
As an example use, one of my pet projects involves user accounts signing up for membership to a user-created group, but the membership profile fields would be set up and customized by the owner of the group. So, one group creator might just want name and email, where another may want those fields, location, job title, and also a little biography. I wouldn't want to store each field as a column, because the table would have a lot of useless columns, so it makes sense to instead store this information as attributes of the user, and just pull the values when required by the group. Any discussion would be appreciated. Thanks! -- You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/turbogears?hl=en.
