In our case, the app we were migrating had PHP and Python scripts accessing the database, so changing a column name would require lots of code changes everywhere else. I'm going to try forking and making the changes to support auth.settings.email_field .
On Thursday, May 31, 2012 5:21:18 PM UTC-7, Anthony wrote: > > But shouldn't people who already have tables and want to use web2py be >> able to rename the default required field names? This would help people >> with existing user tables but different field names for email, password, >> etc. For example, if the 'user' table has 'password_field' instead of >> 'password', 'user_email' instead of 'email', etc. >> > > I suppose that would be nice. Note, you can specify a custom password > field name via auth.settings.password_field, but not for email and > username. If you're simply migrating an existing db/table for use with > web2py, doing a one-time alteration of the field names should be no > problem. The only case not easily covered is when web2py has to share an > existing user db table with another non-web2py application. > > Anthony >
