I was guessing that you were missing a field in your scheduled_task table.  
I don't know when it happened, but at some point an additional field was 
added to the table.  I'm confused as to why your migrate didn't work though 
to rebuild everything.  Well, glad you have it all working now.

-Jim


On Tuesday, November 10, 2020 at 12:04:11 PM UTC-6, Gaël Princivalle wrote:
>
> > Did you go in to the application so that db.py would be executed, 
> thereby triggering the migration to happen? 
> Yes, after each modification of the DB connection string I reload a 
> website page.
>
> I've resolved this problem moving the scheduler tables in another DB.
>
> Thanks for your help.
> Il giorno martedì 10 novembre 2020 alle 15:45:43 UTC+1 Jim S ha scritto:
>
>> Did you go in to the application so that db.py would be executed, thereby 
>> triggering the migration to happen?
>>
>> -Jim
>>
>> On Tuesday, November 10, 2020 at 8:33:41 AM UTC-6, Gaël Princivalle wrote:
>>>
>>> Thank you Jim.
>>>
>>> I've setted migrate to False and fake-migrate to True.
>>> Deleted the scheduler tables in the database folder
>>> Setted migrate to True and fake-migrate to False
>>> And the tables are not rebuild in the DB.
>>> The error still the same.
>>>
>>> I'll try to delete the scheduler.py file, export the db, import it in a 
>>> new db and add again the scheduler...
>>>
>>> Il giorno martedì 10 novembre 2020 alle 15:20:36 UTC+1 Jim S ha scritto:
>>>
>>>> Can you go to the databases directory in your app and delete the 
>>>> scheduler tables from there?  Then make sure your db connection has 
>>>> migrate=True specified along with fake-migrate=False.
>>>>
>>>> I'm thinking that should force a rebuild of the scheduler tables in 
>>>> your database.
>>>>
>>>> -Jim
>>>>
>>>>
>>>> On Tuesday, November 10, 2020 at 3:02:15 AM UTC-6, Gaël Princivalle 
>>>> wrote:
>>>>>
>>>>> I've deleted the scheduler.py file and deleted the scheduler tables.
>>>>> Now if I add again the scheduler.py file the scheduler tables are in 
>>>>> the admin but not in the DB, and the error is the same for all the 
>>>>> scheduler tables, InFailedSqlTransaction.
>>>>>
>>>>> Someone can help me?
>>>>>
>>>>> Il giorno domenica 8 novembre 2020 alle 21:08:45 UTC+1 Gaël 
>>>>> Princivalle ha scritto:
>>>>>
>>>>>> We talk about the db.scheduler_task table. I've deleted all the 
>>>>>> records from this table, and also from db.scheduler_run and 
>>>>>> db.scheduler_worker.
>>>>>>
>>>>>> No way.
>>>>>>
>>>>>> Il giorno domenica 8 novembre 2020 alle 20:57:23 UTC+1 Gaël 
>>>>>> Princivalle ha scritto:
>>>>>>
>>>>>>> Hi.
>>>>>>>
>>>>>>> Someone knows what it means?
>>>>>>>
>>>>>>> After a server change I'm able in the Admin to modify the table 
>>>>>>> records but not the one of the scheduler.
>>>>>>>
>>>>>>> Any idea?
>>>>>>>
>>>>>>> Traceback (most recent call last):
>>>>>>>   File "/home/user/apps/web2py_folder/web2py/gluon/main.py", line 
>>>>>>> 456, in wsgibase
>>>>>>>     session._try_store_in_db(request, response)
>>>>>>>   File "/home/user/apps/web2py_folder/web2py/gluon/globals.py", line 
>>>>>>> 1251, in _try_store_in_db
>>>>>>>     if not table._db(table.id == record_id).update(**dd):
>>>>>>>   File 
>>>>>>> "/home/user/apps/web2py_folder/web2py/gluon/packages/dal/pydal/objects.py",
>>>>>>>  
>>>>>>> line 2686, in update
>>>>>>>     ret = db._adapter.update(table, self.query, row.op_values())
>>>>>>>   File 
>>>>>>> "/home/user/apps/web2py_folder/web2py/gluon/packages/dal/pydal/adapters/base.py",
>>>>>>>  
>>>>>>> line 579, in update
>>>>>>>     raise e
>>>>>>> InFailedSqlTransaction: current transaction is aborted, commands 
>>>>>>> ignored until end of transaction block
>>>>>>>
>>>>>>

-- 
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
--- 
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 web2py+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/web2py/ff906acf-ae85-40fd-9e34-beffa8cbdc5ao%40googlegroups.com.

Reply via email to