DBMS_REDEFINITION set Primary Key column NULLABLE=Yes
Hello everyone,
When I redefine a table, in a schema other than my own, with the copy_constraints=>TRUE option the primary key constraint is
copied but the primary column NULLABLE value is set to YES (the original table had a value = NO).
When the table is in my schema the primary column NULLABLE value is set to NO.
In both scenarios the interim table primary column NULLABLE property = YES.
I wanted to post it here before submitting a SR to oracle.
Do you see this as expected behavior?
Anyone else experience this?
Maybe I'm missing an parameter and/or option.
When I redefine a table, in a schema other than my own, with the copy_constraints=>TRUE option the primary key constraint is
copied but the primary column NULLABLE value is set to YES (the original table had a value = NO).
When the table is in my schema the primary column NULLABLE value is set to NO.
In both scenarios the interim table primary column NULLABLE property = YES.
I wanted to post it here before submitting a SR to oracle.
Do you see this as expected behavior?
Anyone else experience this?
Maybe I'm missing an parameter and/or option.
0