<< Design Factors 15: Rather common model of BLL and DLL classes, what are special cases we need to consider? | Home | Design Factors 17: Where exceptions are thrown for invalid values? >>

Design Factors 16: How the null values are handled?

maui_be

Null values are one of the basic considerations, without taking care of which may raise lots of confusions and errors while the application is running in the live. Some application architecture supports a model which puts null values to the database while the user is providing empty data from the user interface end. For string/text type data some times are saved as empty string (i.e. string.empty). But it creates confusion where empty string itself considered as a value. Also, besides string/text type data, special care are required for other type of data (number, fraction, date time etc) with respect to null values to be saved and retrieved to and from the physical database tables. These considerations are required to be addressed in this point.

Technorati Tags: ,
  • Share This Post:
  • Share on Twitter
  • Share on Facebook
  • Share on Technorati
Print | posted on Monday, April 21, 2008 12:12 PM

Feedback

# re: Design Factors 16: How the null values are handled?

left by Jawwad Alam at 1/6/2009 3:08 AM Gravatar
I think we should always make a field Nullable in the database if its optional. In my view, using string length function to check the existance of data in a field is not a best approach.
Post A Comment
Title:
Name:
Email:
Website:
Comment:
Verification:
 
 
Copyright © Mohammad Ashraful Alam