[ic] Table::DBI set_slice and undefined values

[Bill Carr]

In an effort to optimize MySQL I have added NOT NULL DEFAULT <some
value> to most of my column definitions. According to the Mysql manual
this will result in a smaller data file size and make everything faster.

Now when I insert a row using mv_todo=set I receive an error message:
column can not be NULL.

If I INSERT using the mysql command line any missing fields will be will
contain the DEFAULT values from their column definitions.

Using IC to insert into a database Interchange will make an insert like
this:
	insert into <table_name> (a,b,c) VALUES ('defined value',undef,undef)

How can I get it to do this instead
	insert into <table_name> (a) VALUES ('defined value')

This will let the insert happen without error and the undefined columns
will get set with the default from their col defs.

-- 
Bill Carr
Worldwide Impact
bill@worldwideimpact.com
413-253-6700