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
Removing an attribute
I'm trying out SDDM (v20.2) for a new project but I keep running into (simple?) problems.
Latest problem: If I remove an Attribute from a logical entity, it still shows up in the engineered relational model.
How do I tell SDDM to always "engineer from scratch"?
This "feature" would be fine after the data model was pushed into production. But, I'm still working things out. (including learning this tool)
thanks.
MK
Best Answer
-
Default behavior in engineering is deleted objects to not be selected. You need to select that attribute in order the change to be propagated to relational model.
BTW there is a "tabular view" in engineering dialog and it's more usable in most of cases - you have there text filtering and filtering by type of objects in addition to filtering by status
Philip
Answers
-
You could always delete the relational model and then engineer from logical. I tend not to do engineer to relational until my logical model is pretty solid.
Seriously, tomorrow I may have a chance to switch from my work computer (at work, we have an existing DB so not doing any design work) to my home one and I'll fool around with it to see if there is a better answer to your question.
-
Default behavior in engineering is deleted objects to not be selected. You need to select that attribute in order the change to be propagated to relational model.
BTW there is a "tabular view" in engineering dialog and it's more usable in most of cases - you have there text filtering and filtering by type of objects in addition to filtering by status
Philip
-
I'm still starting out on SDDM.
I "engineer to relational" then "generate DDL" just to make sure all of my settings are to my liking. (naming convention, etc.). Its that first step that was giving problems.
Philip's answer was pretty useful. I don't think things could be faster then that. If so, I'd love to hear about it.
You'll probably see a few more "help!" posts from me later on.
Thanks for the help.
MK