Discussion for FogBugz Plugin developers
I don't agree with this requirement for custom database tables.
A default value must be specified for a column that does not accept NULL.
If we have to specify a default value, then what's the point of specifying that it can't be null? Typically when a column is specified as "not null" it means we want to force the calling code to specify a value for the column.
Sunday, August 23, 2009
You're probably right about this one. We added that requirement for plugin columns because for Join tables we need to be able to insert new rows, so we either need it to be NULLable or have a default value. But we shouldn't need a default for every column.
I've opened a case.
Tuesday, August 25, 2009
This topic is archived. No further replies will be accepted.Other recent topics