For what it's worth Casey, I've been developing with SQL Server, and prior
to that Subase, for a number of years now, and I have never heard anyone say
that fields should be a space instead of NULL.
Personally, I'd leave it as it is!!
N
on 8/9/01 1:52 AM, [EMAIL PROTECTED] at [EMAIL PROTECTED] wrote:
> 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
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Get the mailserver that powers this list at http://www.coolfusion.com
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
