On Jul 15, 11:47 am, [EMAIL PROTECTED] wrote: > > thought it might. In my little MCV world, it's part > > of M, not C or V and I wanted to keep it that way as much as > > possible. It still is, just not in SA. > > i have similar thing into the M/odel, but it is pre_save(), not > after_load(). So it's easier, and done by the sa-managing wrapper. > Though i'm thinking that one day i may need some after_load() - it is > symmetrical to pre-save, and these things go in pairs...
Heh! Oh yes, good thought, and I do some pre_save() massaging as well. But now that you mention it, it's fairly symmetrical conceptually having both parts in my own Model code and not in SA's code. Having Turbogears' model.py *is* after all, part of the "Model". -Paul --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
