mysql - how treat the database record that are not activated or how to prevent it -



mysql - how treat the database record that are not activated or how to prevent it -

we have user table record user sign in our website, might not activate it

our practice 1 time user register, record store in our table, 1 time user click activation link, activation code alter ' ' (empty)

if record did not activated, email can't utilize , in our table

user id | email | activation code 1 | abc@abc.com |asdasdasdadadsasda 2 | cde@abc.com |

whats best practice or solution this?

create new table store activation code , insert user table 1 time activated?

or leave that? there waste store it

or improve solution this?

i used way:

a temporary table containing temporary accounts (not yet activated) a table containing accounts (activated)

thanks this, can spare spaces in main business relationship table , can add together task (for example, each week) remove old temporary accounts.

when user activates account, move info temporary main table.

mysql website

Comments

Post a Comment

Popular posts from this blog

ruby on rails - Devise Logout Error in RoR -

ruby on rails - Devise Logout Error in RoR - while using devise in ror, encountering unusual error when trying log out url different root url. displays me : actioncontroller::invalidauthenticitytoken in devise::sessionscontroller#destroy" for illustration if rooting path after log in '/structure', , seek log out '/general' error, while logging out '/structure' fine. any help highly appreciated. ruby-on-rails ruby devise
Read more

c# - Create a Notification Object (Email or Page) At Run Time -- Dependency Injection or Factory -

c# - Create a Notification Object (Email or Page) At Run Time -- Dependency Injection or Factory - i have code emails me notification when happens. trying add together page , also remove dependency on email. for reference; have name of notification want send stored string in database. @ runtime have list of people , string representation of want receive. i thought dependency injection ninject, kernel bindings got big , seemed hacking together. then thought simple factory, activator.createinstance(email/page) inotifcation, don't know how handle differing constructor parameters (unless utilize common, complex property, employee, has info need). so far have this: public interface inotification { void sendmessage(); } public class email: inotification { private readonly string _toemailaddress; private string body { { homecoming "email"; } } private static string smtphost { ...
Read more

model view controller - MVC Rails Planning -

model view controller - MVC Rails Planning - i'm starting rails , i'm building app stores films info, user can watch film , give grade on web application. i have coded cinema model, controller , views. now, have 2 questions: should need create model , controller grading? in case, should create or should wait , create first users model , controller? yes, on model , controller grades. that'd feasible way maintain track of who's graded what. it's create first, i'd start users, since grades depend on both films , users. ruby-on-rails model-view-controller
Read more