Discussions
Categories
- 196.8K All Categories
- 2.2K Data
- 238 Big Data Appliance
- 1.9K Data Science
- 450.2K Databases
- 221.7K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 550 MySQL Community Space
- 478 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3K ORDS, SODA & JSON in the Database
- 544 SQLcl
- 4K SQL Developer Data Modeler
- 187K SQL & PL/SQL
- 21.3K SQL Developer
- 295.8K Development
- 17 Developer Projects
- 138 Programming Languages
- 292.5K Development Tools
- 107 DevOps
- 3.1K QA/Testing
- 646K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 154 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.1K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 18 Java Essentials
- 160 Java 8 Questions
- 86K Java Programming
- 80 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 204 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 437 LiveLabs
- 38 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 171 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 232 Portuguese
Why does SDDM not allow an index to have the same name as a constraint? DB allows that?

Hi
Why does SDDM not allow an index to have the same name as a constraint on the same table?
e.g. Primary key constraint = FND_ITEM_PK. Defining an index with the same name the index gets append with a v1.
When SDDM is set to auto create indexes for constraints when generating DDL it creates the index with the same name and that DDL is accepted by the DB (Oracle).
When that same table is then imported into a design or the design synchronised from the database, the index will be imported but again the "v1" appended to its name.
If the DB allows for an index to have the same name as a constraint, then why different in SDDM?
Thank you & Regards
Answers
-
Hi,
there is no such restriction. I cannot reproduce that behavior.
You can have index and constraint with the same name but cannot have two indexes or two constraints with the same name - otherwise it's a bug