foo290/Django-Verify-Email

Migration path to add this library into existing project

Opened this issue · 0 comments

mojeto commented

Hi there,
what is the best way to add verify_email into existing project that has active users already?
I want the users to gradually verify their emails without affecting the way they use rest of the system much.
If I install this library it expects linkcounter one to one relation to exist for each user. But this related model instance gets created for new users only.
What is the migration to mitigate this?
Should I create a data migration that creates verify_email_linkcounter data entry for each existing user?
Should the default sent_count be zero in this case?