yep, but every time a scheduler task starts, it executes models to recreate the environment. given that you commit() in your task, the "queueing" gets committed too (that's probably the reason why it worked for you until now)
You can use the uuid column to specify a unique name for your task, in that case when you try to insert a task that is already there the scheduler will refuse to insert a new one (because of the constraint on that column). However, it's silly to have models queueing tasks, cause the "queueing" should happen on-demand, not on every possible request ^_^ -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
