nope, it doesn't, but auth.user_id defaults to None if there is no
logged-in user.
Not sure what happened without having the complete app code, however the
scheduler tables are not meant to be altered, e.g. with common_fields, so
it definitely should have been those to make the scheduler not beh
Ok that appears to have been the problem. Getting rid of
db._common_fields.append(standard_fields) fixed it. Didn't hone in on the
exact problem but maybe it's because I had not null on created_by,
modified_by fields which defaulted to auth.user_id. Does a scheduled task
even have a concept
I created a bare bones app and the scheduler seems to work without error.
Not really sure what's happening with the problem app but if I had to guess
I'm thinking it might be related to using
db._common_fields.append(standard_fields)
where standard_fields is a table with fields such as date_cr
postgresql. Also my app which uses same database works and I can see the
tables and the row in scheduler_task table from appadmin
On Friday, January 10, 2014 9:57:25 AM UTC-5, Niphlod wrote:
>
> what db are you using ?
> that error usually pops up when the scheduler can't access the scheduler_*
what db are you using ?
that error usually pops up when the scheduler can't access the scheduler_*
tables.
On Friday, January 10, 2014 2:09:26 AM UTC+1, User wrote:
>
> I'm just getting started with the scheduler and I'm getting an error when
> I start it on windows 7:
>
> C:\www\web2py>python w
5 matches
Mail list logo
