in an alter table statement, I can do:
ADD COLUMN column-definition
and column-definition is defined as:
{
NOT NULL |
[ [CONSTRAINT constraint-Name]
{
CHECK (searchCondition) |
{
PRIMARY KEY |
UNIQUE |
REFERENCES clause
}
}
}

Since there is no way to say "NULL" (NOT NULL may be specified), one would assume that the default behavior when one omits "NOT NULL", is to produce a column that allows NULL. But derby 10.4 is acting as if NOT NULL is the default. Has something changed in 10.4?

 
-geoff