|
|
|
|
||||||
![]() |
|
|
LinkBack | Outils de la discussion |
|
|
#1 |
|
Messages: n/a
Hébergeur: |
On Mar 24, 2:40pm, --CELKO-- <jcelko...@earthlink.net> wrote:
> >> The fact remains, some things are just that, flags... no further information necessary, no updating required. << > > I define a flag as a binary value which is set by an event. Can you > give me an example of a flag that is set without an event? A flag that shows whether or not a person has access to a given process is an example; we don't care when the access was granted or if they used to have it, we care if they have it now. > People keep trying to model yes/no questions a survey with flags. Go figure... trying to use a data type with two possible value to hold something with two possible values. Outrageous! > They get screwed up when they need more status codes such as "not answered", "N/ > A", "contradictory", etc. As you so nicely put it: "Real world design > and development dictates a little more flexibility than that." For a simple yes and no question, NULL works just fine for a question that isn't answered. |
|
![]() |
| Outils de la discussion | |
|
|