Discussions
Categories
- 196.7K All Categories
- 2.2K Data
- 235 Big Data Appliance
- 1.9K Data Science
- 449.8K Databases
- 221.5K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 549 MySQL Community Space
- 477 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3K ORDS, SODA & JSON in the Database
- 532 SQLcl
- 4K SQL Developer Data Modeler
- 186.8K SQL & PL/SQL
- 21.2K SQL Developer
- 295.3K Development
- 17 Developer Projects
- 138 Programming Languages
- 292K Development Tools
- 104 DevOps
- 3.1K QA/Testing
- 645.9K Java
- 27 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
- 390 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
- 1K Español
- 1.9K Japanese
- 230 Portuguese
Synonyms not saved anymore in Physical Model on Import Data Dictionary (19.4 and 20.2)

Hello,
For a special delivery developers have created a new schema containing ~60 Synonyms to existing Views in other schemas.
Updating the existing data model with Synonyms fails with data modeler version 20.2 and 19.4.
I had to switch back to 18.4 to achieve the update of the existing data model with the new "Unknown Synonyms".
Within the import dialog the new Synonyms are listed as New and are detected. Hitting the Merge button does not save the changes in the design.
Performing the same activity within 18.4 does save the synonyms after the merge.
SInce there was a discussion on Supporting formats via Save As. I did Save As in 20.2, Data Import, Merge and Synonyms are not saved in Design.
I assume it is an Bug related to designs initially created with an older version of the datamodeler.
Creating a new design did show all synonyms, but I did not test any "Update" activities. Since I have to maintain for documentation purposes 80+ Subviews starting from scratch is not an option, I will stick on 18.4
Thx in advance for any input on how to resolve my problem
Walter
Answers
-
Hello,
thanks for reporting the problem. I logged a bug.
The problem is in merging. Synonyms are stored in target object - that means that in current version you cannot save synonym if target object (the one in FOR clause) is not in the model.
Philip
-
Hello,
Thank you for your answer. Do you haven an ETA for a fix ?
One of my long term tasks on Todo list is documenting how "external" views to be used by customer relate to each other. The new feature implied foreign keys from 19.4 is perfect for this task, but cannot be used in 18.4.
Walter