On Sep 29, 11:46 am, Christoph Zwerschke <[email protected]> wrote: > Am 29.09.2010 16:43, schrieb Luke D: > > > 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? > > Did you see dictlike.py and dictlike-polymorphic.py in examples/vertical > in the SQLAlchemy package? > > -- Christoph
Yeah, I think those SQLAlchemy examples are exactly how I would setup my model, but I guess I wasn't sure how that would affect the rest of the Turbogears application and coding it. It just seems like such a different paradigm than most of the TG stuff I've looked at. For example, one of the things I can't wrap my head around is how the user membership setup page would be coded to allow someone to create profile attributes for their membership requirements. Any thoughts? -- 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.
