On Jul 1, 2010, at 8:24 PM, Michael Bayer wrote: > The Column object contains a "sort key" when constructed, against a single > global value, that is used as a sort key when the Table is generated. This > is to get around the fact that the attribute dictionary of the declarative > class is unordered.
Interesting. I guess I didn't come across this in the source. I actually ended up implementing a similar thing in a subclass I have of column (I think I'm doing some stuff that isn't very standard) Since we're talking about columns, I also noticed that copy() doesn't copy the .info object over. > > The mixin columns should copy their "sort key" over, or it should somehow be > tailored in the declarative base so that the order of the two columns stays > relatively the same, and perhaps is also tailored to be at the same position > relative to the other columns in the ultimate table. > > I'd welcome any patches in this regard since I don't usually deal with the > "mixin" feature. -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalch...@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.
