The Database Design Resource Center

Great! Agree! Thank you!

by Marcus
(Sao Paulo, Brazil)

I am developing a small ERP and needed to decide today whether to use NULL columns or not. I was already inclined towards not using, mainly because of disturbing things like SUM() results. When your article first mentioned "assumption", I was sure of the way to go: no NULLs!

Your examples are great, your argueing too. Thank you very much! Made my Sunday!

Just one more consideration: while NULL is not a good invention as a "data type", it is helpful when doing LEFT JOINs to exclude rows from a SELECTION. Is this right? Or would there be a solution without NULL?

Regards,

Marcus

Click here to post comments

Join in and write your own page! It's easy to do. How? Simply click here to return to On NULL values.


Exclusive interviews with:
Steven Feuerstein, PLSQL expert
Donald Burleson, Top IT consultant


Free eBook

Subscribe to my newsletter and get my ebook on Entity Relationship Modeling Principles as a free gift:


What visitors say...

"I just stumbled accross your site looking for some normalization theory and I have to say it is fantastic.

I have been in the database field for 10+ years and I have never before come across such a useful site. Thank you for taking the time to put this site together."

Mike, USA

Read more Testimonials

Database Normalization eBook:


Database Normalization eBook



Copyright © www.databasedesign-resource.com / Alf A. Pedersen
All rights reserved.
All information contained on this website is for informational purposes only.
Disclaimer: www.databasedesign-resource.com does not warrant any company, product, service or any content contained herein.

Return to top

Copyright acknowledgement note:

The name Oracle is a trademark of Oracle Corporation.
The names MS Access/MS SQL Server are trademarks of Microsoft Corporation.
Any other names used on this website may be trademarks of their respective owners, which I fully respect.