Discussions
Categories
- 197K All Categories
- 2.5K Data
- 546 Big Data Appliance
- 1.9K Data Science
- 450.8K Databases
- 221.9K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 552 MySQL Community Space
- 479 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.1K ORDS, SODA & JSON in the Database
- 556 SQLcl
- 4K SQL Developer Data Modeler
- 187.2K SQL & PL/SQL
- 21.4K SQL Developer
- 296.3K Development
- 17 Developer Projects
- 139 Programming Languages
- 293K Development Tools
- 110 DevOps
- 3.1K QA/Testing
- 646.1K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 158 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.2K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 19 Java Essentials
- 162 Java 8 Questions
- 86K Java Programming
- 81 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
- 205 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 468 LiveLabs
- 39 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 175 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 233 Portuguese
Partial use of foreign key attributes

Quite some time ago I asked this in a similar form already. But as it always hinders me in design and implementation (and, in getting 0 differences when synchronising data dictionary with model), I like to discuss/request it again.
In my logical model, there is in an entity b having some foreign key attributes coming from a relationship between entity a and entity b. Let's say entity b has 5 fk attributes from entity a. I only need 2 of them as primary key attributes (together with some more attributes of the entity b).
In this example, I can set the 2 FK attributes as PK attributes and save the design, but as soon as I reopen it, all 5 foreign key attributes are automatically checked as PK attributes again. As entity b has relationships to other entities (entity c, d, ...), it has quite a lot of unwanted impact, i. e. creating unwanted foreign key attributes in these other entities.
And, of course, if I engineer the logical model to the relational model, the unwanted attributes are transferred to unwanted columns.
My request is to allow for exactly the PK attributes I need , independently of being it a FK attribute or another attribute. That would help a lot.
Thanks and regards,
Robert
Best Answer
-
Hi Robert,
thanks for reporting the problem, logged a bug. In 20.3 - it'll work for none identifying relationships.
Philip
Answers
-
Hi Robert,
thanks for reporting the problem, logged a bug. In 20.3 - it'll work for none identifying relationships.
Philip
-
Hi Philip
Very good news! And having this functionality already in version 20.3. is of course very much appreciated. I am looking forward to define non-identifying relationships this way.
Best regards,
Robert