you can put them on like in every table, and then prevent the scheduler migrating the table setting migrate=False in its call. There should be no problems on that, but a big problem arises : the scheduler_task table will likely to have multiple copies of the same task (auditing works in that way, setting to "is_active" only the last version of the record but keeping the entire history) and will try to execute all of them.
anyway, why do you need to audit the task table ? Il giorno venerdì 18 maggio 2012 10:43:38 UTC+2, szimszon ha scritto: > > Hi! > > I wonder if somebody could help me. > > I have to audit scheduler_task > db.scheduler_task._enable_record_versioning() works but scheduler_task have > no Created On, By and Modified On, By (is_active) Fields :( > > Can we put this Fields in it? >
