On Sunday, June 10, 2012 2:16:51 PM UTC-5, Jonathan Lundell wrote: > > On Jun 10, 2012, at 8:38 AM, Brad Miller wrote: > > My latest hypothesis is that this is a bug in fake_migrate ?? I'm using > 1.99.4 on webfaction, and I'm using 1.99.7 on my development box. > > > That was my thought, given what you posted. > > > When I turn on fake_migrate_all=True the .table file generated for > auth_events does not match the actual table. > > So, I'm wondering about upgrading the version of web2py on webfaction... > Does anyone have any experience with that? Is it as easy as replacing the > web2py directory they created for me with the latest source and then > restoring my application directories??? > > > I don't know. If it's a stock web2py directory, you'd think so. (Or maybe > you could just move the good .table file from your development box? There > are other reasons you might want to update web2py, though.) >
The upgrade seems to have worked. My production app is still running great. -- But I haven't migrated it over to the new naming scheme for my .table files, and I won't until I know it will work and I won't have a broken production app!
