>> yes and no, as i said i'm replacing the __dict__ with something >> special; so >> its IA riding on top of me (;-) but otherwise its that. no renaming, >> i dont >> want someone (thats can be me, later) to be able to workaround >> either me or SA. > > then have your magic __dict__ implement the same "save committed on > change" behavior as the attributes package. and of course test on > every SA release (i know, it broke only 6 times this year ;-) >since youre welded to internal behavior: > > def my_magic_dict_set_something(dict, key, value): > if key not in dict['_state'].committed_state: > dict['_state'].committed_state[key] = _the_old_value > dict[key] = value > thanks, thats different idea to what i had in mind... i'll try..
--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
