Posted by binder on 10/02/62 11:54

binder wrote:
> I am designing a new table with a few columns that may or may not have
> a value on each row that is inserted.
>
> What issues determine whether to allow a NULL value to be inserted for
> that column or define a default value to be used?
>
> I want to think through the repercussions of this decision before I get
> into production.

>From a programmatic standpoint, if I have a column that may or may not
have a value, is it better to insert a default value that indicates no
value was entered, such as 0 for a userid, or insert a NULL value?

[Back to original message]