We are still running 0.6.4 so I think that was the only way to implement events (set/append/remove), correct?
On Aug 25, 12:38 pm, Michael Bayer <mike...@zzzcomputing.com> wrote: > ho boy. Why are you playing with instrumentation ? That's a really obscure > feature we created literally for one product. I'd love to blow it away. > Anyway, if that's the error its giving you, then that's definitely one of its > limitations :). > > On Aug 25, 2011, at 11:10 AM, Kent wrote: > > > > > > > > > Assume I have a class hierarchy: > > > class Base(object): > > __sa_instrumentation_manager__ = AttrManager > > > class Order(Base): > > __sa_instrumentation_manager__ = OrderAttrManager > > > This causes "TypeError: multiple instrumentation implementations > > specified in Order inheritance hierarchy:" > > > I don't understand why or how I can go about overriding the > > AttributeManager for a specific class. I want 95% of the classes to > > use AttrManager, but I want a specific one for OrderAttrManager. > > > What am I doing wrong? > > > -- > > 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 > > athttp://groups.google.com/group/sqlalchemy?hl=en. -- 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.
