Is null implicitly inserted as value on nullible columns w/no default? 1

[Coder7]

Good morning all.

A general question:

If I have a nullible column, no default set, when I do not explicitly insert a value into the column (i.e. value = getDate()), is NULL always implicitly inserted as the value?

Are there caveats/pitfalls if I don't explicitly insert the NULL value?

I am working with stored procedures that were written by 2 contractors who are supposed to be sql server gurus but I've had to fix enough of their sql to become wary.

Thanks, as always, for sharing your expertise.

Have a great week.

 

[swampBoogie]

If I have a nullible column, no default set, when I do not explicitly insert a value into the column (i.e. value = getDate()), is NULL always implicitly inserted as the value?

Yes, null will be stored (unless the column has an identity attribute).

 

[Coder7]

Thanks for the speedy reply, swampBoogie.

Now I can have peace of mind (about this issue at least haha).

 

[wyldsider]

Actually, not to mix words, but as NULL implies the absence of any value, wouldn't it be more correct to say that no value is stored so that the "value" of the column remains NULL?

cheers,
Jack

Jack De Winter
Software Developer
MedTel Software

http://www.medtel.on.ca