On Jul 1, 2011, at 1:19 AM, Russ wrote: > > The only thing I'm still unsure of in the code is why mapper.columns > is a collection and it required checking columns[0], but I can either > just live with that or look into it later.
because an attribute can be mapped to multiple columns, i.e. http://www.sqlalchemy.org/docs/orm/mapper_config.html#mapping-a-class-against-multiple-tables . as I did this example and thought back upon how often people want to poke around the mapper configuration, i started trying to think of how to turn the mapper hierarchy into a more of a well described DOM-type of system. In this case one thing I thought of would be to add a "first_column" accessor to ColumnProperty. -- 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.
