Discussions
Categories
- 196.7K All Categories
- 2.2K Data
- 235 Big Data Appliance
- 1.9K Data Science
- 449.9K Databases
- 221.6K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 549 MySQL Community Space
- 478 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3K ORDS, SODA & JSON in the Database
- 532 SQLcl
- 4K SQL Developer Data Modeler
- 186.9K SQL & PL/SQL
- 21.3K SQL Developer
- 295.4K Development
- 17 Developer Projects
- 138 Programming Languages
- 292.1K Development Tools
- 104 DevOps
- 3.1K QA/Testing
- 645.9K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 153 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.1K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 17 Java Essentials
- 158 Java 8 Questions
- 85.9K Java Programming
- 79 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.2K Java SE
- 13.8K Java Security
- 203 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 400 LiveLabs
- 37 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.6K Other Languages
- 2.3K Chinese
- 170 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 230 Portuguese
Generate 12c Identity clause

Jeff's blog post describes how to generate an identity column. This procedure generates a DDL statement like:
CREATE TABLE table_name (
id NUMBER(18)
GENERATED BY DEFAULT
AS IDENTITY
This structure does not allow a null to be included in the insert statement. However, some applications do issue INSERT statements with the ID column.
The solution (as explained here) is to generate the DDL with the 'ON NULL' as:
GENERATED BY DEFAULT ON NULL
AS IDENTITY
Question: How do I do this in SQL Developer Data Modeler?
PS: In an earlier version of this post, I indicated that APEX applications run into this problem. I since learned that, APEX allows you to set a "Query Only" switch on the ID column that prevents this problem.
Answers
-
These are the steps that I follow, there might be other ways also:
Now, I engineered to Rational and gradually Physical models:
Physical Model:
My DDL:
-
one more picture
it's better identity clause to be set in preferences and only for fluctuations to go at column level in physical model (>= Oracle DB 12c)
Philip