Tefnet Developers wrote: > > Dnia 2009-07-28, wto o godzinie 11:06 -0400, Michael Bayer pisze: > >> A few things here. First is, I'm not observing the extension not >> getting >> inherited. Task().result = 3 raises the error, DeliveryTask().result = >> 3 >> does not, and the value is assigned to 3. This is with 0.5.5 as well as >> trunk. > > [...] > >> So the sub column_property() needs to >> reference the original Column: > > Hm, I fixed it to reference the parent's column, but still:
having a MapperProperty "override" a MapperProperty on a base class, while it "works", is something SQLA has never supported (since they typically represent columns, which don't "inherit" in SQL), and we've only just begun to support it in limited cases for concrete table inheritance. so if you can boil down each behavior you see to a self contained test case we can start to add each use case to our test suite. If you're in a hurry, you might want to pursue other styles that don't involve MapperProperty's inheriting. I'd consider the specifics of each class validation being associated with each class for which a single attribute extension on the base class consults. This can be the dictionary approach I outlined, or a distinct callable, and if you don't like it attached directly to the class you can place it in a registry. There's dozens of ways to do this without the need for inheriting SQLA properties. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" 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/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
