I'm developing a corporate network, and I'd like to check it every time the user logged in, whether or not he activated his account via the token sent to his email. But I do not want this check to be done all the time, is that possible?
For example, as long as the user does not activate their account, the system will check to see if the flag in the database "enabled" is as true , but after it becomes true , this account would never need to be checked again because it has already been activated.
Regardless of the technology (language) used, I would like to know if it is computationally possible, through some logic, to create an algorithm that was used until a certain parameter was met, and after that the code "would no longer be executed" (would be discarded from the source code, something of the kind). Because it depends on a particularity that needs to be verified, but once verified as true it would not be necessary to have this code snippet anymore, however each user has his particular token verification, he could not simply remove it from the code, since in some time either user would need the verification.
Postponing is not trivial, it is more conceptual, whether it is possible or not, regardless of the language used.