maybe another way is to abandon mapperExtension and make that via column's default_value function (or even server-side function) - if u dont need doing anything else there.
On Wednesday 05 November 2008 11:47:37 Yap Sok Ann wrote: > I use a MapperExtension to automatically put the current timestamp > into a updated_at column for all entities. This works fine except > when related entities get involved. Let's say I have a Many-To-One > relation between employees and departments. If I switch the > department for an employee, even though nothing has really changed > for the department instance, both employee and department instances > will get a new timestamp. I would like to know what is the best way > to just update the employee and skip the department. > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
