No, .table files aren't deleted or corrupted. Most of the output are of the type
timestamp: XXX ALTER TABLE YYY DROP COLUMN ZZZ; faked! Regards Abhishek Gupta Co-founder, Zumbl Zumbl <http://zumbl.com> | Facebook<http://facebook.com/abhishekgupta.iitd> | Twitter <http://twitter.com/abhishekgupta92> | LinkedIn<http://linkedin.com/in/abhishekgupta92> On 23 May 2013 23:42, Anthony <abasta...@gmail.com> wrote: > I was just wondering because I think writing to sql.log should only happen > when there are actual changes to the table definitions (or if the *.table > files are deleted or become corrupted). If you're not making any changes to > the schema or touching the *.table files, I wouldn't think the sql.log file > would fill up so quickly. What do you see in it? > > Anthony > > > On Thursday, May 23, 2013 1:58:39 PM UTC-4, Abhishek Gupta wrote: > >> 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. >> >> Regards >> Abhishek Gupta >> Co-founder, Zumbl >> >> Zumbl <http://zumbl.com> | >> Facebook<http://facebook.com/abhishekgupta.iitd> | >> Twitter <http://twitter.com/abhishekgupta92> | >> LinkedIn<http://linkedin.com/in/abhishekgupta92> >> >> >> On 23 May 2013 23:23, Anthony <abas...@gmail.com> wrote: >> >>> Are you doing something that requires fake migrations every day >>> (presumably multiple times per day)? Are the *.table files getting deleted? >>> >>> >>> On Thursday, May 23, 2013 12:04:32 PM UTC-4, Abhishek Gupta wrote: >>> >>>> Anthony, that souns good, thanks. >>>> Massimo, our sql.log grows to almost 1GB each day. I used >>>> fake_migrate=True for all the tables. >>>> >>>> Regards >>>> Abhishek Gupta >>>> Co-founder, Zumbl >>>> >>>> Zumbl <http://zumbl.com> | >>>> Facebook<http://facebook.com/abhishekgupta.iitd> | >>>> Twitter <http://twitter.com/abhishekgupta92> | >>>> LinkedIn<http://linkedin.com/in/abhishekgupta92> >>>> >>>> >>>> On 23 May 2013 19:25, Anthony <abas...@gmail.com> wrote: >>>> >>>>> I believe sql.log only records the SQL for migrations (i.e., table >>>>> creation, altering tables, and truncating tables), so logging will be >>>>> disabled if you disable migrations. >>>>> >>>>> Anthony >>>>> >>>>> >>>>> On Thursday, May 23, 2013 12:16:20 AM UTC-4, Abhishek Gupta wrote: >>>>>> >>>>>> Hi, >>>>>> >>>>>> Is there an easy way to disable the logs generated in >>>>>> databases/sql.log other than editing gluon/dal.py? >>>>>> >>>>>> Regards >>>>>> Abhishek Gupta >>>>>> Co-founder, Zumbl >>>>>> >>>>> >>>> >> -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
