This content has been marked as final. Show 1 reply
Hi,1 person found this helpful
Yes, this is to be expected. The current version of Workspace Manager only has support for check constraints, not the null/not null keyword. Check out my 1st response to the following thread, as it is related.
Re: Why is null field blank in describe of version-enabled table?
Essentially, you can do both operations currently, you just need to operate on the check constraints themselves. After beginDDL is called, you would want to drop the check constraint from the _LTS table, instead of declaring the column not null. After calling commitDDL, the constraint would then be removed from the base table. Similarly, currently when adding the constraint, only the check constraint is actually being transferred. This is sufficient to ensure that that data is not nullable, but the column would continue to appear as nullable by the SQL*Plus describe command and the tabcolumns views.
Support for the null/not null keywords should be added in a future version.