I tested that out and here is what I found:
This is the generated script:
CREATE TABLE Dz2cpr.T_CDE_CMS_TOS
CDE_CMS_TOS CHAR(1 BYTE),
DSC_CMS_TOS VARCHAR2(100 BYTE)
CREATE UNIQUE INDEX Dz2cpr.I_CDE_CMS_TOS ON dz2cpr.T_CDE_CMS_TOS
ALTER TABLE Dz2cpr.T_CDE_CMS_TOS ADD (
USING INDEX Dz2cpr.I_CDE_CMS_TOS
The new table was created w/o the NOT NULL settings for both fields.
The file differences report shows:
Comparison of TABLE T_CDE_CMS_TOS in D@DSST1 and TABLE T_CDE_CMS_TOS in D@DSST1
2/7/2017 8:32:48 AM
L3 CDE_CMS_TOS CHAR(1 BYTE) NOT NULL,
R3 CDE_CMS_TOS CHAR(1 BYTE),
L4 DSC_CMS_TOS VARCHAR2(100 BYTE) NOT NULL
R4 DSC_CMS_TOS VARCHAR2(100 BYTE)
From: John Dorlon [mailto:firstname.lastname@example.org]
Sent: Tuesday, February 07, 2017 8:13 AM
Subject: RE: [Toad for Oracle - Discussion Forum] Issue with create table script and not nulls
RE: Issue with create table script and not nulls
Reply by John Dorlon
Some NOT NULL constraints are automatically created by Oracle when you create a primary key. In these cases, our script does not also specify NOT NULL for these columns because if you do that, then you’ll end up with double not null constraints on those columns.
Try recreating the table with the script that Toad gives you and then compare the created table vs the one that you made the script from. If you spot any differences, let me know.
To reply, please reply-all to this email.
Stop receiving emails on this subject.
Unsubscribe from Toad for Oracle Forum notifications altogether.
Toad for Oracle - Discussion Forum
this post as spam/abuse.