I found it.
It was in db.py
db.define_table('frame',
Field('framename', type='string',
# #unique=True,
the problem. Is it
a bug ?
label=T('Framename')),
sorry for being late. This is from web2py's 2.6.0 changelog.
Attention MySQL users: The length of string fields changed from 255 to 512
bytes. If you have migrations enabled this will trigger a large migration.
To prevent it, first set migrate_enabled=False, upgrade, check everything
is ok,
Just wanted to chime in on this.
For me, I had to add a length=255 to all my unique=True fields, even
after adding length=255 for the string fields.
On Wednesday, October 9, 2013 11:46:48 AM UTC-7, Niphlod wrote:
sorry for being late. This is from web2py's 2.6.0 changelog.
Attention MySQL
My gut feeling says mysql 5.1 -- mysql 5.5 upgrade is the cause. Am I right ?
And how do I solve it. :-)
*Error ticket for adeploy*
*Ticket ID*
192.168.2.106.2013-10-08.12-46-19.24f3f1a5-d637-4522-965b-fed4958115ed
*class '_mysql_exceptions.OperationalError' (1071, 'Specified key was too
Ok, I am now fighting with it for two days and it drives me crazy.
My gut feeling says mysql 5.1 -- mysql 5.5 upgrade is the cause. Am I right ?
And how do I solve it. :-)
*Error ticket for adeploy*
*Ticket ID*
192.168.2.106.2013-10-08.12-46-19.24f3f1a5-d637-4522-965b-fed4958115ed
*class
Upgraded from 2.5.1 to 2.6.0, and it seems that auth.wiki is causing this.
If I comment it out, everything else works fine.
#auth.wiki(resolve=False)
#wiki = Wiki(auth=auth, render='html')
Ticket ID
127.0.0.1.2013-08-03.08-03-20.34cb1611-c6d4-46fc-b59e-106ad21d723e
class
6 matches
Mail list logo
