TOAD 13 named 'not null' constraint script different

Toad for Oracle
1

After upgrading to TOAD 13 I noticed the generated scripts were different for ‘not null’ named constraints.

TOAD 12.12

ALTER TABLE LBS_ACTION_JN MODIFY

JN_OPERATION CONSTRAINT LBS_ACTIONJN_OPER_NCHK NOT NULL
ENABLE VALIDATE;

TOAD 13.0

ALTER TABLE LBS_ACTION_JN ADD (

CONSTRAINT LBS_ACTIONJN_OPER_NCHK
CHECK (“JN_OPERATION” IS NOT NULL)
ENABLE VALIDATE);

The second script adds a constraint but does not make the column ‘not null’ in the table description.

Found this post which explains the difference:

https://asktom.oracle.com/pls/apex/asktom.search?tag=named-not-null-constraint

2

Yes, those are definitely different kinds of constraints. I refer to the latter as a “fake not null” Toad 12.12 and prior could create scripts for those accurately. But I always thought 12.12 ran more queries than it really needed to, so I made some changes.

On Toad 13.0, it comes out right on SB-Tables-Script but I see what you mean on SB-Constraints-Script tab.

I’ll am logging the bug and will have it fixed soon. Thanks for letting me know.