the the migrate settings is about the define_table affect on the database side (migrate = True) and on the *.table files (fake_migrate=True). there will be a little performance impact, but in terms of efficincy code (because you only need to execute 1 time for create index). So let say about study case in here, imagine that you have to use the other database backend say mysql or postgresql, yet to create index is not support "IF NOT EXIST", yet you will be 'check mate' in the case you put the CREATE INDEX in the models. or put it simple just throw away IF NOT EXIST and keep it with your SQLITE, you will got an error said the the index already created.
best regards, stifan -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- 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/d/optout.
