Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
cesark
Posting Yak Master
215 Posts |
 Posted - 2008-03-11 : 13:06:59
|
| I have a users table with a field to register the date the user was registered for the first time, and another field to register the user’s ‘reason’ of that registration. Now I’ m considering to add a field to register drops (when the user decides not continue with us, or we decide it). To do that I am considering to add a field to register ‘drop’ date, and another field to determine if the user is ‘active’ or ‘inactive’ (registered or dropped..? How is called this in English?), and another field to register the user’s reason of dropping (resignation). So, the users table would include:UserState (Registered or Resigned (Dropped?))RegistrationDateRegistrationReasonResignationDateResignationReasonIs this the common way to handle user’s registration and resignation in a database?Thank you,Cesar |
|
|
jsmith8858
Dr. Cross Join
7423 Posts |
|
|
cesark
Posting Yak Master
215 Posts |
Posted - 2008-03-11 : 17:32:18
|
| Once they have resigned, they will not have access to the web application.To come back later they would have to 'register' again, since this might happen, will be rare cases, but I have to consider them. |
 |
|
|
|
|
|
Handle user’ s registration and resignation