If the field def'n were to be changed to [ col2 NUMBER DEFAULT ON NULL 0 ] and then when I insert/update something that becomes NULL and the result becomes 0 for that field, then yeah, bingo.
On Wed, Oct 8, 2014 at 2:14 PM, Petite Abeille <petite.abei...@gmail.com> wrote: > > On Oct 8, 2014, at 6:14 AM, Stephen Chrzanowski <pontia...@gmail.com> > wrote: > > > When adding a NULL value to a table that has the NOT NULL flag set on > that > > field, instead of raising an exception, if the field definition were to > > have the word "USE" between "ON CONFLICT" and "DEFAULT" in its > declaration, > > it'd use whatever the fields default value was set to. If USE is > included, > > the DEFAULT value must be included, otherwise the table isn't created. > > Oh, wait… isn’t that what an other, unnamed database does? [1] > > E.g. DEFAULT ON NULL > > [1] > http://www.oracle-base.com/articles/12c/default-values-for-table-columns-enhancements-12cr1.php#nulls > > > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
