what I actually wanted to do is this. when my app runs for the first time it has the auth user table (renamed to tv_auth_users), around 20 columns and 2 records. the structure of other auth_tables remains same. But the tv_auth_permissions table has around 40 records and tv_auth_membership and the tv_auth_groups have 3 records each. So I thought if I put these in a seperate file it would speed up the app. I didnt know how to write the db.py file for such a scenario.
On Friday, 16 August 2013 20:38:00 UTC+5:30, Niphlod wrote: > > > > On Friday, August 16, 2013 4:32:26 PM UTC+2, ajith c t wrote: >> >> Thank you Niphold for your time and patience. So actually there isnt any >> particular benefit in writing in a dump file and loading. Its better to >> write these definitions in another db.py (like mydb.py) file and load. Then >> I would be able to get it in the db.py. Thanks >> >> Not sure of what you mean, but if you don't need to restore any data (so, > you need only the schema) is definitely faster to let web2py manage it on > an empty database. > -- --- 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.
