yep, a new column was added and it's defined to be unique. When it gets created if you have n rows already in the table the values in the column are not unique, hence the error. If no rows are in the scheduler_task table, no error should show up.
On Thursday, August 30, 2012 2:23:18 PM UTC+2, Tyrone wrote: > > It appears that it's an incompatibility with the original tables, when I > delete everything the problem goes away. I got around the problem by > deleting everything, and then overwriting the new database with the old > one, excluding the scheduler tables. --
