Re: Interesting question and debate on ddl tables with datefieldsthatwill not always have a value

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

For the most part, probably not. I once tried to give a brief talk on
simple Boolean logic to a group of users who wanted to learn how to
write reports using a report writing tool. I was amazed at how opaque
the subject was to most of them. If NOT, AND and OR are unfathomable
subjects, NULL probably is too.

Pete Hall
pbhall@xxxxxxxxxxxxx


Mike Cunningham wrote:

So far this discussion has been focused on IT professionals and the proper user of null fields. What happens when you bring a non-IT user into this discussion and they are using some package to query that same database. Are these employees going to understand the concept of a null field and how to get the correct results from their query when a field is null capable? Will they understand that field = blank is not the same as field = null?

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkj2tVcACgkQpcZsDl8OX6nlPACdGK2hD4pkqBSyiI85WoIOUk8P
KsoAnRtViMCC1Ye8tQebMmvJFvFjkl6G
=JuNG
-----END PGP SIGNATURE-----