No, we aren't doing anything that requires fake_migrations to be true. I did it because of the peculiar needs that we had :
Live Server - One domain - One database
Dev Server - Multiple domains/web2py installations - Shared database
Generally, when we make any change in db, I set migrate=True for that table which make changes to the shared database, and then, manually migrate the table using SQL syntax to the live server. But I think migrate=False should work equally well too, and I shouldn't thus be required to worry about the logging.