No that would have give an Operational Error (because it would have been database error, not a web2py error). I do know why this problem. Never seen it before.
On Aug 28, 12:46 am, Richard <[email protected]> wrote: > I deleted database/*.table and now it works, so looks like a migration > problem with upgrading. Could this be related to the "radical" > proposal to change the default string lengths? > > Richard > > On Aug 28, 3:09 pm, Richard <[email protected]> wrote: > > > I upgraded to latest version of web2py and now I am getting this error > > (not sure if those 2 events are related): > > > Traceback (most recent call last): > > File "/home/web2py/gluon/restricted.py", line 178, in restricted > > exec ccode in environment > > File "/home/web2py/applications/studio09/models/db.py", line 75, in > > <module> > > db.Field('type', 'integer', default=INITIAL_TYPE), > > File "/home/web2py/gluon/sql.py", line 1008, in define_table > > query = t._create(migrate=migrate) > > File "/home/web2py/gluon/sql.py", line 1370, in _create > > sql_fields_old = cPickle.load(tfile) > > EOFError > > > any ideas? > > Richard --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
