I have a pretty simple case. A base class with three sub-classes, and then
a final class that inherits from the three derived classes. When
persisting, sqlalchemy only sets the properties of the parent class and the
first child class.
In all other respects the sub-class is behaving properly;
using declared_attr instead of declaring the attributes directly did not
help. now I'm going to try the strategy of referring to the existing table
attribute.
(on 0.8.2b2, fwiw)
~ethan
--
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To view
I am all down with the power of mixins. The reason I mapped things this way
is because I do have concrete instances of string, amount, and quantity.
(I'm capturing data from receipts: string can be e.g. a receipt number,
amount can be e.g. a total, and quantity can be something unaffiliated