And it works well. Thanks.
--
On Wednesday, September 19, 2012 8:09:24 PM UTC+10, Tim Richardson wrote:
>
>
>
> On Wednesday, 19 September 2012 19:17:32 UTC+10, Niphlod wrote:
>>
>> a column with a unique costraint was added. Given that you had a
>> scheduler_table not empty, that newly added column was giving you the
>> pr
if you drop the table you need to delete also the
databases/*_scheduler_task.table file, otherwise web2py does not know that
the table does not exists.
Il giorno mercoledì 19 settembre 2012 12:09:24 UTC+2, Tim Richardson ha
scritto:
>
>
>
> On Wednesday, 19 September 2012 19:17:32 UTC+10, Niphl
On Wednesday, 19 September 2012 19:17:32 UTC+10, Niphlod wrote:
>
> a column with a unique costraint was added. Given that you had a
> scheduler_table not empty, that newly added column was giving you the
> problems.
> What did you do when you say "I deleted the scheduler_task table" ?
>
I use
a column with a unique costraint was added. Given that you had a
scheduler_table not empty, that newly added column was giving you the
problems.
What did you do when you say "I deleted the scheduler_task table" ?
Il giorno mercoledì 19 settembre 2012 09:38:39 UTC+2, Tim Richardson ha
scritto:
>
I found a post from August 30 with the same problem. One tip was to delete
all records from the scheduler_task table, but I still received the error.
Then I delete the scheduler_task table, and now the app generates a ticket
saying that it can't find the scheduler_task table.
This also happens i
6 matches
Mail list logo
