the reason that get_history calls attribute_manager.get_history is because all awareness of "attribute history" is handled by the attribute module. the reason attribute_manager then calls the InstrumentedAttribute off of the class is because thats where AttributeManager reprents the behavior for a specific class attribute. ColumnProperty knows nothing about InstrumentedAttribute.
if you look at the constructor for InstrumentedAttribute itself, youll see it takes two callables which provide the "compare" function and the "copy" function. these are provided by the TypeEngine object via the ColumnLoader, which is off the ColumnProperty. So i would propose that these two arguments become optional keyword arguments to ColumnProperty which ColumnLoader/DeferredLoader pick up on and send to their init_class_attribute method, so that you can send in whatever compare and copy callables you want. --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
