Please drop the scheduler_worker table from the database and remove the file *_scheduler_worker.table from the databases/ folder of your application, then set migrate to True (a single request with migrate=True will suffice). The table will be recreated properly and the error will go away.
The error comes from the fact that the adapter chooses "at connection time" the "nicest" column type to play with based on the backend version. The definition of the scheduler_worker table has a "json" Field, that on postgresql 9.3 maps to a "json" column, while on 9.1 was a "text" column, hence the misbehaviour if you don't drop and re-create the table. -- 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. For more options, visit https://groups.google.com/d/optout.
