On Jul 2, 2011, at 2:25 PM, Russ wrote: > > I know very little about your internal implementation, but I might as > well toss a thought out there on navigating a mapper configuration... > it would be more intuitive/explicit to me if there were a > DbColumnProperty base class, and two derived classes: > SingleDbColumnProperty and MultiDbColumnProperty (and I guess you > would need RelationProperty, and probably more). The former with a > simple .column attribute, and the latter with your current .columns > sequence attribute.
I try to avoid requiring the use of isinstance() to navigate a hierarchy. Ideally there'd be just one kind of "node" (right now, mapper or column(s)) and one kind of "edge" (currently column property, relationship property, as well as some others like synonym property). When working with a DOM like elementtree, you know what kind of "node" you're on based on how you got there, i.e. did you look at ".tail", "children", "attr". Hence the idea of ".columns" as well as "first_column", i.e. like jquery's ":first". I'm having kind of a big idea on this now. like an 0.8 kind of thing.... -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com. To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
