Database design suggestion needed

[-]

Hi,

I have the following table:

CREATE TABLE user_account
(
id....
email_address ......
password .......
activated...
......
)

where the email_addres serves as the username. When a user signed up for
an account, the 'activated' entry defaults to 'off'. The user will then
have to check his email account and go to a link to activate the account.

What I would like to do is make the email_address changeable and the
user has to verify that the new email addres is valid by again visiting
a link first.

This means that the new email address has to be stored somewhere.

There are two options that i can think of.

1) Create a new table as follows:

CREATE TABLE updated_email_address(
(
user_account_id...
new_email_address...
)

2) Store the new email into the user_account table.

CREATE TABLE user_account
(
id....
email_address ......
new_email_address <--------------
password .......
activated...
......
)
Design wise, which is the prettiest method?
Or is there another solution besides the above two?

Thank you.

[Aggro]

- wrote:

Design wise, which is the prettiest method?
Or is there another solution besides the above two?

From those two, I suggest using the same table. One extra column won't
do much harm, it's 1-1 related to the other material in the same table,
and queries and checking is much simpler with the data in same table.