I need to your opinions:
Currently our database allows nulls on all fields besides primary
keys and fields we have specified as wanting a default value. We now
have database support outside of ourselves and their opinion is to
not allow nulls and have a default value of a "blank space". Is there
a reason to populate "blanks" vs. allowing nulls as defaults within
any given table.
My opinion:
If the database has been started with allowing nulls in fields then
why change to defaulting "blank spaces" mid stream and confuse the
developers from today moving forward. I need to know if I'm off
target here.
Your input is greatly valued.
Casey Cook
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
