Data Modeler - applying naming standards to relational model

Hi,
first of all thanks for the new data modeler build (584) - it really fixed some issues (e.g. unique keys with non mandatory referenced ids are now persistent) ...
BUT ... why is there an option to disable foreign key names when applying naming rule although it does not work?
I like my primary key names etc. to follow some naming rules, but I don't like foreign keys to follow rules, just because neither "Benutzer_Id3" follows the company internal naming rules nor is it very easy to understand at all.
Steps taken:
* logical model is complete
* generate relational model
* foreign key names are as intended (e.g. "User_Id_Modifier")
* right click the relational model
* click "Apply Naming Standards ..."
* remove the check mark from "Column Foreign Key"
* click "OK"
The foreign key column is changed regardless of checkbox state :-( - even deselecting all check boxes still applies naming rules to the foreign key columns.
Is there a fix/workaround for that or need I to go back to build 570?
Thanks god I still have my 570 compatible model ins SVN
regards stueckl

Hi,
unfortunately that functionality for all tables in relational model is broken - you still can use it at table level - "Naming rules" button in table dialog.
Philip

Similar Messages

Problem with Applying Naming Standards to Keys and Constraints

Hi
I have an issue, and not sure where to go. I have 3 relational models in 1 design. I set up my foreign key template. I applied it to the first relational model, and it worked like a charm. When I bring up the "Apply Naming Standards" window for the second model and click on OK, nothing happens. The window just stays there and the OK button turns gray. I checked the log, but no messages are written. I just have to click on cancel to close the window. Has anyone got any suggestions on what to do? I even went back in and changed a table name to make sure that a foreign key name should change, and still nothing happens.

Hi Joep,
thanks for design. I logged bug for that problem - some FK columns keep information about non existent foreign keys.
Here is a transformation script you can run for relational model:
columns = model.getColumnSet().toArray();
for (var t = 0; t<columns.length;t++){
column = columns[t];
nodes = column.getRefColAndAssocIDs().toArray();
for (var i = 0;i<nodes.length;i++){
node = nodes;
if(node.fkAssocId!=null){
fk = column.getDesign().getDesignObject(node.fkAssocId);
if(fk==null){
column.removeFKAssociation(node.fkAssocId);
column.setDirty(true);
And of course you have to save design - it's better to use "save as".
Philip

Data Modeler 3.0 EA1 - Logical Relation to Foreign Key not generating

When use "Engineer to Relational Model" the only time it creates foreign keys from my relations is when those relations are of the type many-to-many. I've added a Primary UID for each table and I have tried to use the Apply Naming Standard options but nothing seems to work.
I tested my design with the design rules feature I have no errors.
Does anyone have any ideas?
Greg

Hi Greg,
probably you added primary uid after first engineering to relational model. You can check whether those uids are selected in engineering dialog.
Also you can check log file in datamodeler\datamodeler\log directory for logged problems there.
Philip

'Engineer to Relational Model' Dialog does not open

Steps to reproduce:
Open Modeler.
Create a Glossary file with one row as ATTRIBUTE & ATTR as Name & Abbreviation respectively. Check "Incomplete modifier".
Goto Naming standards under preferences, choose that glossary file. In the logical model, create an entity with one attribute "ATTRIBUTE 1".
Right click logical model, click 'Engineer to Relational Model', goto General Options tab, check "Apply Name translation". Click Engineer.
You'll see ATTRIBUTE is not changed to ATTR in the relational model.
Now right click logical model again, click 'Engineer to Relational Model'. Nothing happens now.
Goto Naming standards under preferences, double click the glossary file, uncheck Incomplete modifier", save & close.
Now right click logical model again, click 'Engineer to Relational Model'. It works now. But still the abbreviation does not happen in the relational model.

Sorry for the very late reply.
My version is this -
Version 3.1.0.700
Build 700
And my fresh log file is below (it shows an error. but I dont think that is related with the problem that I am having now)
2012-06-26 05:59:44,639 [main] INFO ApplicationView - Oracle SQL Developer Data Modeler 3.1.0.700
2012-06-26 06:00:12,440 [Thread-13] ERROR XMLTransformationManager - Unable to load object from XML: D:\Lenin\CODE EU\Adhoc Subject Wise\mapping\ExtendedMap_RM6FC65D48-B203-C5D5-5BDE-6BF8B4199E5A.xml
java.io.FileNotFoundException: D:\Lenin\CODE EU\Adhoc Subject Wise\mapping\ExtendedMap_RM6FC65D48-B203-C5D5-5BDE-6BF8B4199E5A.xml (The system cannot find the file specified)
     at java.io.FileInputStream.open(Native Method)
     at java.io.FileInputStream.<init>(FileInputStream.java:106)
     at oracle.dbtools.crest.model.metadata.XMLToObjectTransformer.transformToObject(Unknown Source)
     at oracle.dbtools.crest.model.metadata.XMLToObjectTransformer.transformToObject(Unknown Source)
     at oracle.dbtools.crest.model.metadata.XMLTransformationManager.transformFromXMLToObject(Unknown Source)
     at oracle.dbtools.crest.model.metadata.XMLTransformationManager.transformFromXMLToObject(Unknown Source)
     at oracle.dbtools.crest.model.design.Design.openDesign(Unknown Source)
     at oracle.dbtools.crest.swingui.ControllerApplication$1.run(Unknown Source)
UPDATE:
I have downloaded the latest version (Version 3.1.1.703 Build 703) and opened my model.
Now I am not able to engineer to relation model in any option (tried checked and unchecked "incomplete modifiers")
When I right click logical model and click engineer to relation model, I get an empty dialog box with a warning icon and a OK button - but no message in it.
Here is my log file:
2012-06-26 07:02:48,643 [main] INFO ApplicationView - Oracle SQL Developer Data Modeler 3.1.1.703
2012-06-26 07:03:22,288 [Thread-14] ERROR XMLTransformationManager - Unable to load object from XML: D:\Lenin\CODE EU\Adhoc Subject Wise\mapping\ExtendedMap_RM6FC65D48-B203-C5D5-5BDE-6BF8B4199E5A.xml
java.io.FileNotFoundException: D:\Lenin\CODE EU\Adhoc Subject Wise\mapping\ExtendedMap_RM6FC65D48-B203-C5D5-5BDE-6BF8B4199E5A.xml (The system cannot find the file specified)
     at java.io.FileInputStream.open(Native Method)
     at java.io.FileInputStream.<init>(FileInputStream.java:106)
     at oracle.dbtools.crest.model.metadata.XMLToObjectTransformer.transformToObject(Unknown Source)
     at oracle.dbtools.crest.model.metadata.XMLToObjectTransformer.transformToObject(Unknown Source)
     at oracle.dbtools.crest.model.metadata.XMLTransformationManager.transformFromXMLToObject(Unknown Source)
     at oracle.dbtools.crest.model.metadata.XMLTransformationManager.transformFromXMLToObject(Unknown Source)
     at oracle.dbtools.crest.model.design.Design.openDesign(Unknown Source)
     at oracle.dbtools.crest.swingui.ControllerApplication$1.run(Unknown Source)
2012-06-26 07:03:22,482 [Thread-14] ERROR XMLTransformationManager - Unable to load object from XML: D:\Lenin\CODE EU\Adhoc Subject Wise\mapping\ExtendedMap_RMED70BF0B-C36C-7627-EDDD-1F53A7EAF80F.xml
java.io.FileNotFoundException: D:\Lenin\CODE EU\Adhoc Subject Wise\mapping\ExtendedMap_RMED70BF0B-C36C-7627-EDDD-1F53A7EAF80F.xml (The system cannot find the file specified)
     at java.io.FileInputStream.open(Native Method)
     at java.io.FileInputStream.<init>(FileInputStream.java:106)
     at oracle.dbtools.crest.model.metadata.XMLToObjectTransformer.transformToObject(Unknown Source)
     at oracle.dbtools.crest.model.metadata.XMLToObjectTransformer.transformToObject(Unknown Source)
     at oracle.dbtools.crest.model.metadata.XMLTransformationManager.transformFromXMLToObject(Unknown Source)
     at oracle.dbtools.crest.model.metadata.XMLTransformationManager.transformFromXMLToObject(Unknown Source)
     at oracle.dbtools.crest.model.design.Design.openDesign(Unknown Source)
     at oracle.dbtools.crest.swingui.ControllerApplication$1.run(Unknown Source)
Edited by: emaillenin on Jun 26, 2012 4:36 AM

Renaming Foreign Keys in the Relational Model

Hi,
I'm new to Data Modeler, we are using v 3.0.0.66.5 and Oracle 11g, and I'm trying to build a Logical and Relational model for a new application.
We always name our Primary Keys as ID, this is causing me a problem with my Foreign Keys names in the Relational Model, as they are showing as ID#. Is there a way to add the abbr. of the table to the Foreign Key?
Thanks in Advance
Sue

I always do that job using Naming Standard Templates. This sequence renames ALL FK COLUMNS for ALL TABLES only in RELATIONAL MODEL:
-Preferences > Data Modeler > Naming Standards > templates
-into the box "Column Foreign Key"
-Put something like that: {ref table}_{ref column}
-Then, go into your modeler tree, select the relational model, right click and use "Apply Naming Standards to Keys and Constraints"
-deselect all
-select the last option "Column Foreign Key"
-Go.
What if the names still collide? What if you want to do the job for some--but-not-ALL tables? forget the method above. A transformation script will do that.
You'll need some of these building blocks:
- table.getFKAssociations()
- keys.getRemoteTable().getAbbreviation()
- column.setName()
I'm novice to script coding, sorry I can't assemble a scripted solution right now.
Edited by: T. on May 31, 2011 8:50 AM

Column Prefix from Logical to Relational Model

Hi,
is there any option, that data modeler append an prefix (table short name) to a column, when the logical model will be transformed to relational model? (Same behavior as Oracle Designer)
Example:
Logical Model
TABLE: PERSON
TABLE-SHORT: PERS
COLUMN-1: ID
COLUMN-1: NAME
Relational-Model
TABLE: PERSON
COLUMN-1: PERS_ID
COLUMN-2: PERS_NAME
Kind Regards,
Stefan

Thanks for your answer!
This Script is not really working for me, because of our foreign keys.
All our Foreign-Keys are named "ID" (for nummeric column) or "INDEX" (for a varchar column). After the transformation form logical to relational all the foreign-keys are named like "ID1", "ID2", "ID3", "INDEX1", "INDEX2" etc.
There is no way to apply this script before the foreign-keys where added in the tables?
The Second Way is to create a new script for this task.
am i the only one with this problem? :-/

External table to relational model

Hi,
During a data dictionary import, tables, views, mat views and sequences are "propagated" up to the relational model level, but external tables do not. I think it would be useful if external tables could also be "brought up" to the relational level since an external table is only a different kind of physical structure.
Regards,
Gellért

I am seconding the request to be able to use External tables in the same manner that tables can be used within the Data Modeler. they can be imported into the Physical model, but not in the relational models.

Datamodeler - Naming Standards - technical white paper no longer available?

Hi,
I am wondering, is this document no longer available?
http://www.oracle.com/technology/products/database/datamodeler/pdf/DataModelerNamingStandards.pdf
I a m trying to learn how to apply Naming standards in data modeler but i cannot retrieve this document.
On the datamodeler homepage, on tab "Documentation"
clicking "Naming Standards (Technical White paper - pdf)"
keeps me redirecting into the tab "Overview"
regards,
E.
As I look at the content description of this document(i found that content description somewhere on the www), i believe i would find it very helpfull
Contents of this Oracle SQL Developer Data Modeler Naming Standardization reference guide
Introduction ............ 1
Overview . 2
Defining Templates for Keys, Indexes and Constraints....... 3
Applying the Templates to the Relational Model ............. 5
Prefix Management ........... 6
Setting Name Patterns for Elements..... 7
Defining Word Classification Types .. 8
Supporting Naming Patterns with SQL Developer Data Modeler ... 8
Reviewing Separator Settings for Elements in a Logical Model ..... 9
Reviewing Additional Settings for Elements in a Relational Model . 9
Using a Glossary .. 10
Defining Glossaries ......... 10
Using the Glossary Editor 10
Importing Glossaries........ 12
Importing a CA Erwin Data Modeler Naming Standard Glossary . 13
Using Abbreviations............. 13
Using the Name Abbreviations Utility............. 14
Name Translation . 16
Setting Model Level Name Restrictions ............. 18
Using Design Rules Validation Related to Naming Standards ......... 19
Conclusion ........... 20
Resources ............ 20

it's temporary problem and document will be available soon.
Meanwhile you can look at this thread Data Modeler: Naming
Philip

DataModeler v3.3.0 - Naming standards template for surrogate keys creation

I'm using DM 3.3.0.734 and in the logical model we now can define in the entity properties to "Create Surrogate Key".
When we use Engineer to relational model, for each entity is automatically created a new column using the naming template {entity}_ID as NUMERIC (without precision) and is defined as primary key.
My questions are:
Is possible to define a different naming standard for surrogate key creation?. We define id_{entiry}
Is possible to set the precision of NUMERIC surrogate key?
If we define entity's column as Primary UID, these columns are included in an unique constraint, but are using the naming standards for PK.
As consequence are created the following:
Unique constraint name: entity_PK
Primary key(surrogate)name: entity_PKv1
There is any way to define naming standards like "{entity}_UID" for unique constraints, or even, "{entity}_SK" for surrogate primary key name?
Can anyone help with some of these topics?
Regards,
Ariel.

Hi Ariel,
Naming standards template for surrogate keys creation I logged enhancement request for that.
How to change those bad names (going to change them one by one is not an option):
1) If those "transformed" unique keys are the only ones you have in relational model then simply can apply naming standards
2) You can write transformation script to do that for you
3) you can use new functionality - search, export to excel file, change the names there (using find/replace will be faster) and return changed data back to relational model
you can find description for that here:
https://apex.oracle.com/pls/apex/f?p=44785:24:13179871410726::NO:24:P24_CONTENT_ID,P24_PREV_PAGE:6621,16
http://www.thatjeffsmith.com/archive/2012/11/sql-developer-data-modeler-v3-3-early-adopter-search/
http://www.thatjeffsmith.com/archive/2012/11/sql-developer-data-modeler-v3-3-early-adopter-collaborative-design-via-excel/
You should search for _PK, then filter result on Index and you can export result using report functionality (to XLS or XLSX output format). You can create template and include only table and name (of index) as properties to be included into report.
Regards,
Philip

Sql Developer Data Modeler 3.0 EA1: Preference- Naming standard- Templates

I am trying to figure out how the naming standard templates work.
When I go to:
Preference -> Naming standard -> Templates
It says that 'Attribute Relation' is '{ref entity} {ref attribute}'
What is the consequence of this?
I thought, it would mean that when creating a primary key attribute (ID) on an entity (DEPARTMENT), the related "foreign key" attribute (that is automatically created in related detail entities, such as EMPLOYEES) would be named DEPARTMENT ID.
Instead it is just called ID. Is that the intended behavior?
- Marc de Oliveira
Edited by: marc66 on 2010-10-29 05:59

Marc,
you should check "FK Attribute name synchronization" setting in "Preferences>Data Modeler>Model>Logical model" - probably it's checked and you cannot change the name of FK attribute.
I found another bug here - FK attribute doesn't follow changes in referred entity - I logged it in bug database. As workaround you can apply defined templates at entity level (there is button in entity dialog) or for whole logical model (using pop-up menu in the browser).
Philip

Enforcing use of class word as naming standard via data modeler preferences

Using data model preferences, I have set both the "attribute" and "column" naming standards to have mandatory name parts of both "prime word" and "class word". I have also used data model preferences to specify a glossary that has several terms of type "class word" defined.
My assumption is that if I set a column naming standard preference to have class word as a mandatory name part, then I can apply the default design rules in my relational model and it will list an error "column with wrong naming standards" if any of my column names don't have a name part that is on the list of class words in the specified glossary. Is that assumption correct? If so, it doesn't seem to be working for me...
How does SDDM determine if a class word is missing? I.e., how can I enforce a naming standard that all attribute/column names must have a class word from our approved list of class words?
Thanks!

My assumption is that if I set a column naming standard preference to have class word as a mandatory name part, then I can apply the default design rules in my relational model and it will list an error "column with wrong naming standards" if any of my column names don't have a >name part that is on the list of class words in the specified glossary. Is that assumption correct? yes it's correct.
If so, it doesn't seem to be working for me...one of the settings cannot be changed - it's "Abbreviated only" in "Preferences>Data Modeler>Naming Standard". So only abbreviated part from glossary is taken into account - I logged bug for that.
You can change it - it's in dl_settings.xml file in your design's directory - find - abbreviated_only="true".
How does SDDM determine if a class word is missingIt needs glossary and separator setting.
You can read more here http://www.oracle.com/technetwork/developer-tools/datamodeler/datamodelernamingstandards-167685.pdf
Also can look at examples here Data Modeler: Naming
Philip

Problem with naming of FK attribute when generating the relational model

I'm usign Data Modeler 4.0 and I have a problem when I engineer from Logical model to Relational model.
I have a table SUBJECTS with an unique identifier called ID (pk) and a table BOOKS related to SUBJECTS with a relation named FK_SUBJECT_BOOK and FK attribute named ID_SUBJECT.
When I engineer to Relational Model, it transforms the original FK attribute ID_SUBJECT of the Logical model into an attribute called SUBJECTS_ID in the Relational model.
How can I mantain the name defined in the Logical model also in the Relational model, without using abbrevation and without applying name translation when generating the relational model?
Thank you

I have already tried it. The problem is that if I check the option you mention, then it uses the pk as it is in the related table creating attributes like ID1, ID2, ID3 and so on for all the relations you have.

Logical Model Naming Standard (Title Case) and Foward ENGINEERING how to???

Hi,
I just installed the datamodeler v3.3.0.747.
I want to use the Title Case style as separator style in my logic Model... To do this, i go to the Preferences Settings (Tools > Preferences > Naming Starndard > Logic Model) and set the Title Case as separator Style...
However, when i do foward engineering of the logical model... The Style is omitted and everything is like the logical model... For example,
If i create an entity called: ManagedAccount, i will expected that when i do fwd enginnering, the table associated to that entity will be call as Managed_Account; However, i still getting ManagedAccount...
So, What am i doing wrong??? or this is a bug???
Thanks!

Hi,
in order to get it working in current release you need to create glossary even empty one and set its property "Incomplete Modifiers" to true (check the check box with that name), and to to add that glossary in "Tools>Preferences>Data Modeler>Naming Standard".
We'll change it in next release to work without glossary for this particular case.
Philip

Select schemas from relational model on import from data dictionary option

Hi All,
I have one relational model with 3 diferent schemas,
I want to compare one of my schemas with the data dictionary I have in a database,
I select the import option in the general file menu, select from data dictionary option,
select the connection from my database,swap target model checked,select a physical model and select the objects i want to compare from the database,
My problem is that the result is the comparison between all the objects in my model and the objects in the database that I have selected,
what I really want is to compare a list of objects in my model to a list of objects in my database,
this could be possible? or always need to compare all the objects of the model?
Thanks in advance

Hi jbellver,
there is no any development in DM 3.1.0.691 on that problem. In production release you'll be able to compare objects in subview with database or just to select several objects and compare them with database. And of course "generate in DDl" filtering still can be used - it works at "Compare dialog" level.
Philip

Synchronizing Column Comments from Relational Model to Data Dictionary?

I've changed/added column comments to a table in my Relational Model. When I try to sync the changes to the Data Dictionary of the Database the new/changed column comments are never included. I can actually see that the values in the Field "Comment in RDBMS" are different in the Compare Models Preview Window but the line is not highlighted in red as I expect, in fact it is even grayed out. I also can't check the corresponding checkbox "selected".
Is there a way to get the comments to synchronize? Do I miss any option I have to set first? Ist this a bug or expected behaviour?
I'm using version 4.0.3 x64 of Data Modeler.
Any help would be much appreciated,
Charlie

Hi Charlie,
The greying out of the "Comment in RDBMS" property would suggest that you have filtered out this property for Column objects in a previous Compare.
To unset the filtering, repeat the sync, and when it displays the Compare Models dialog, select the Options tab and then the Properties Filter tab below it.
Select "Columns" in the left pane, and then find the entry for the "Comment in RDBMS" property in the right pane. The "Included" check box should be set.
You can then select the Refresh Trees button below these two panes.
If you then go back to the Details tab, any differences in the "Comment in RDBMS" property for Columns should now be highlighted in red.
David

Data Modeler - applying naming standards to relational model

Similar Messages

Maybe you are looking for