I think the best way to accomplish this is by pulling emails out into another model and establishing a one-to-many relationship between emails and users. Backwards compatibility is going to be a little weird, because we're using the email as the user's fax tag right now.
Easiest way to move forward is to:
- Create a
fax_tag column on the users table
- Copy
user.email over to user.fax_tag
- Create a table called
user_emails with user_id and email columns.
- Go ahead and create a
user_email for all existing users, with the required attributes.
- Drop the
users.email column.
- Verify that all pages and actions are still working with these changes.
We'll also want to make sure the wiki page for updating PhaxMachine instances is created and describes how to run migrations. Other than that, users should have to do nothing, and everything should work much the same as it has previously.
I think the best way to accomplish this is by pulling emails out into another model and establishing a one-to-many relationship between emails and users. Backwards compatibility is going to be a little weird, because we're using the email as the user's fax tag right now.
Easiest way to move forward is to:
fax_tagcolumn on the users tableuser.emailover touser.fax_taguser_emailswithuser_idandemailcolumns.user_emailfor all existing users, with the required attributes.users.emailcolumn.We'll also want to make sure the wiki page for updating PhaxMachine instances is created and describes how to run migrations. Other than that, users should have to do nothing, and everything should work much the same as it has previously.