Added is_verified column to users with default value false

[shubhscoder]

Fixes #3849

1. Added is_verified column to users to with default value false

Thanks!

[shubhscoder]

@Radhikadua123 I am deleting the previous PR and as you said I have made this PR for #3849
Now I will start working on #3848
I am thinking of using the following method:

1. Add a column to the users table to store the unique token that is generated for the user.
2. Implement a function generate_token(user,expiry_time) that will generate a randomized token for the user. This function also stores the generated token in the database.
3. Implement a function validate_token(user,token) that will validate the token and also clear it from the database as the link would be a one time link. This function will also update the is_verified field for the user.

What I am not getting is how are we using the expiry time?

[shubhscoder]

Also, I need some help on finding out why did the test fail and what can be done to fix it. Thanking you in advance.

[Radhikadua123]

@shubhscoder The approach which you are following, needs saving token into the db. But it would be better if we don't save token in db at all. To know how to implement that up, you can check out approach 2 on this comment #3522 (comment)

Do let me know in case you have any doubts regarding that approach.

About the failing test, @jywarren can you please help us out ? I'm not much aware of the environment, but shouldn't the travis CI delete db before running rake db:setup ? And then run rake db:migrate.

[shubhscoder]

Okay so we can use the second approach. It won't require the addition of one more column. We will have to use some gem to get the encryption and decryption done.

[Radhikadua123]

@shubhscoder Encryption/Decryption was added in #3801

[Radhikadua123]

Deferred to #3907

[Radhikadua123]

I saw that you removed these changes from #3907

That's a good practice to make atomic changes in the PR.

So, I'm reopening this PR.

[Radhikadua123]

@jywarren Since I'm new to rails, I'm inexperienced with db changes. Though the column addition definition seems fine to me.

Can you please review this PR ?

Also will it cause down time during the time migration will be ran on the db ? Is that a concern for us ? Any idea ? Also may be @icarito knows about it.

[jywarren]

Hi, no, it won't create significant downtime, no worries! So, now you have to update the /db/schema.rb.example file to reflect the new changes (just those related to your updates) and this should build properly.

Thanks!!!