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 |
|
alex_808
Starting Member
16 Posts |
 Posted - 2014-07-15 : 11:28:30
|
| I have a table of users and I am adding a new field of bit type has_accepted_email_updates. In the application I will prompt the user to ask if he would like email updates with the following options Accept/Refuse/Remind Later. If the user selects Remind Later I will prompt again on each login until he Accepts or Refuses. Now my question, is it good practice to make the has_accepted_email_updates NULL by default and in my application, verify if NULL and prompt the user until the field is not NULL and is either 1 or 0. Or is it better practice to create another bit field prompt_user and use that to decide to prompt rather then testing NULL on has_accepted_email_updates?Thanks Alex |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2014-07-15 : 12:49:26
|
| I would not add another column when has_accepted_email_updates serves the purpose.Tara KizerSQL Server MVP since 2007http://weblogs.sqlteam.com/tarad/ |
 |
|
|
|
|
|
Database Design Best practice