from reading a couple threads around the "NOT NULL" constraint for UCanAccess, I come to the conclusion that there is a fundamental difference between HSQLDB and MS Access, in which HSQLDB forces users to deal with nulls before a NOT NULL constraint can be applied to a column.
Is the team currently considering to implement ALTER COLUMN NOT NULL ? or is this feature unplanned for the reasonable future?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
from reading a couple threads around the "NOT NULL" constraint for
UCanAccess, I come to the conclusion that there is a fundamental difference
between HSQLDB and MS Access, in which HSQLDB forces users to deal with
nulls before a NOT NULL constraint can be applied to a column.
Is the team currently considering to implement ALTER COLUMN NOT NULL ? or
is this feature unplanned for the reasonable future?
hello,
from reading a couple threads around the "NOT NULL" constraint for UCanAccess, I come to the conclusion that there is a fundamental difference between HSQLDB and MS Access, in which HSQLDB forces users to deal with nulls before a NOT NULL constraint can be applied to a column.
Is the team currently considering to implement ALTER COLUMN NOT NULL ? or is this feature unplanned for the reasonable future?
It's unplanned because unsupported by jackcess, we can't alter the
underlying metadata structure if jackcess doesn't allow us for this
Il Mar 8 Dic 2020, 23:35 Jefferson Poe jeffersonatsafe@users.sourceforge.net ha scritto:
thanks for confirming that Marco!