Funny thing - After this happened, I re-built all my tables (allowing web2py to do so) and after that everything worked ok for that database. 4 of my other apps working off the same server did not work and I didn't have time to recreate the DBs. Well yesterday I updated from trunk again and all of a sudden my re-built database no longer worked. Same error as below. But, all of my old DBs started working again.
Am I losing it, or did something change with the MySQL adapter and then change back with the latest release yesterday? -Jim On Tuesday, April 24, 2012 1:02:24 PM UTC-5, Jim S wrote: > > Hi > > I've recently updated my MySQL test server to version 5.1.61 on Ubuntu. > > In my db.py I specify my field names with mixed case. > > In my.cnf I have: > > lower-case-table-names = 1 > > In the past this has always worked for me. But today, once I upgraded > MySQL, I'm getting the following on any request to any of my apps: > > Traceback (most recent call last): > File "C:\dev\web2py\gluon\restricted.py", line 205, in restricted > exec ccode in environment > File "C:/dev/web2py/applications/mustangs/models/db.py" > <http://127.0.0.1:8000/admin/default/edit/mustangs/models/db.py>, line 76, in > <module> > format='%(heading)s') > File "C:\dev\web2py\gluon\dal.py", line 6677, in define_table > polymodel=polymodel) > File "C:\dev\web2py\gluon\dal.py", line 795, in create_table > fake_migrate=fake_migrate) > File "C:\dev\web2py\gluon\dal.py", line 861, in migrate_table > and not isinstance(table[key].type, SQLCustomType) \ > File "C:\dev\web2py\gluon\dal.py", line 7105, in __getitem__ > return dict.__getitem__(self, str(key))KeyError: 'newsitemid' > > > In the database, the field name is newsItemId. > > Anyone else seeing this behavior with the latest MySQL on Ubuntu? My > other MySQL tools are working as you'd expect regardless of the case I use. > > -Jim > >
