S
Simon
Hi all,
Do you think the best way to avoid the problems of nulls in the database is
just to provide default values via the db schema?
Alternatively, is it better to allow nulls, seeing as the "absence" of data
is an entirely valid and useful value?
If the later is true, is there a better way to handle nulls that doing this
for each and every column of each and every table? I'm hoping there is
something a bit more intuitive or something that would write this crap for
me the way I want (without me having to learn a CG scripting language for
customised templates)?
I'm really more interested on everyones thoughts on the first two questions
though.
Many thanks all
Simon
Do you think the best way to avoid the problems of nulls in the database is
just to provide default values via the db schema?
Alternatively, is it better to allow nulls, seeing as the "absence" of data
is an entirely valid and useful value?
If the later is true, is there a better way to handle nulls that doing this
for each and every column of each and every table? I'm hoping there is
something a bit more intuitive or something that would write this crap for
me the way I want (without me having to learn a CG scripting language for
customised templates)?
I'm really more interested on everyones thoughts on the first two questions
though.
Many thanks all
Simon