Sql datamodeler: Engineer to relational model

Hello
is it possible to add a prefix to all your tables?
Suppose I have entities A, B and C
Than I would like to have the following tables as a result
XYZ_AS, XYZ_BS and XYZ_CS
This according to the CDM standards
Regards Erik

Erik,
it's possible to replace one prefix with another one in current published build (525). It'll be possible to add (replace) prefix to all tables or to tables in certain subview in next release. There won't be possibility to change name A to name XYZ_AS; there will be no problem to change names A and B to XYZ_A and XYZ_B.
Best regards,
Philip

Similar Messages

Sql datamodeler: Engineer to relational model: General Options

Hello
When you engineer your logical model to a relational model you get a wizard. In lower part of this wizard byou have several tabs, one of the tabs is called general.
On this general tab you have check box: Apply Name Translation
The corresponding help text:
Apply Name Translation: Controls whether formal names are translated to abbreviated names when the logical model is forward engineered to a relational model, and whether abbreviated names are translated to format names when a relational model is reverse engineered to the logical model. Name translation is applied only for valid names. In addition, translations between the words entity/attribute/key and table/column/index are performed.
Does anybody have a clue what is meant here?
Regards Erik

Erik,
you have to create glossary (tools>Glossary editor) with words permitted for usage in names in logical model. For each word you can define abbreviation that will be used in transformation process.
Example:
Employee - EMP
Salary - SAL
Attribute "Employee Salary" will be transformed to column "EMP_SAL".
You can define preferred abbreviation for entities and attributes and it can be used instead of glossary definitions.
You also have to set your glossary in "Tools>General Options>Naming standards>Glossary"
Best regards,
Philip

SQL Datamodeler: engineer to relational model: column names

Hello
Suppose I have an attribute called DAY OF BIRTH. Is there a way I can forward engineer this attribute to a column name DAY_OF_BIRTH?
(I know you could have a coulmn name "day of birth" but thats not what I want)
Regards Erik

Hi Erik,
1) you should check separator settings in General options>Naming Standard -it should be "space" for Logical model and "underscore" for Relational model;
2) "Apply name translation" should be selected in engineering dialog
Best regards,
Philip

Engineer to Relational Model: deleted attributes / undeleted columns

Hello,
I am using Datamodeler 3.3.0.744.
I'm modifying an existing logical model: I'm deleting one or more attributes in an Entity.
Then I'm executing "Engineer to Relational Model" in oder to get an up to date Relational Model (it existed already).
The corresponding columns are not deleted in the Relational Model, even though attributes don't exist anymore at the logical level.
I can't find any option available in order to do that...
In the previous release (3.1), it worked fine, I could choose the behavior related to the deleted attributes (deleting or not deleting corresponding columns).
Edited by: user4995029 on 27 mai 2013 02:43

When your forward engineer for a 2nd time you should see a dialog that has the logical on the left and the relational on the right. Entities that are new or changes have an exclamation point next to them. If you open that you will eventually drill down to see the attribute/columns. Where your dropped an attribute it will say "To drop". The check box is unchecked by default. If you check it then when you forward engineer those should get dropped from the associated table.
Is it not working that way in 3.3?

'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

Engineer to Relational Model - subtypes have no attributes.

Hello.
Engineer to Relational Model tool don`t show attributes of subtype entity. Some bug or feature?
DM 3.1.0.687.

1) Funny, when I dropped the column, and had it recreated by the engineering process, it worked correctly. But re-engineering the old column kept setting it to mandatory even when I manually set it to optional. I have a sense that some of my objects are ignored by the tool... Only when I drop them and recreate them they seem to be recognized. I had the same issue with some entities that consistenetly did not got engineered into my relational model. Only when I created a new ER-diagram and included the same entities they would get engineered into the relational model...
2) Designer did this. When a supertype table was generated in the "one table" mode there would always be a new column called SUBTYPE with a constraint allowing the short names of each subtype as values (ex: for the table PARTIES the SUBTYPE column could only contain the values PERS and ORG). With this in place you could create constraints such as "SUBTYPE = 'PERS' and FIRST_NAME is not null or SUBTYPE = 'ORG' and FIRST_NAME is null".
Regards,
Marc de Oliveira

Logical model fwd engineer to relational model. Missing FK relationships

We are experiencing missing relationships in the relational model when engineering from logical model to the relational model. The logical model objects have properly defined primary keys defined. We are using SQL Data Modeler v3.1.700. Any suggestions on how to engineering these relationships without deleting the objects from the relational model.
Thanks,
Ed

Hi Ed,
I presume you had some relationships in the Logical Model that you were expecting to be engineered to Foreign Key relationships in the Relational Model.
Please can you provide more detail to help resolve your problem. For example:
Was the problem on an initial engineer from the logical model? Or on a re-engineer?
Are you using Entity subtyping in your Logical Model?
Are there any relevant error messages in the log file? (This is normally file datamodeler.log in folder datamodeler\datamodeler\log.)
David

SDDM EA 3.1: Engineer to Relational Model (subtypes)

It seems that mandatory attributes of entity subtypes become mandatory columns on the corresponding tables even when you engineer to "one table" (the super type).
In that case I would expect that the column would become optional.
Even better: a check constraint would verify that the column was not null for records belonging to the originating subtype.
/ Marc de Oliveira

1) Funny, when I dropped the column, and had it recreated by the engineering process, it worked correctly. But re-engineering the old column kept setting it to mandatory even when I manually set it to optional. I have a sense that some of my objects are ignored by the tool... Only when I drop them and recreate them they seem to be recognized. I had the same issue with some entities that consistenetly did not got engineered into my relational model. Only when I created a new ER-diagram and included the same entities they would get engineered into the relational model...
2) Designer did this. When a supertype table was generated in the "one table" mode there would always be a new column called SUBTYPE with a constraint allowing the short names of each subtype as values (ex: for the table PARTIES the SUBTYPE column could only contain the values PERS and ORG). With this in place you could create constraints such as "SUBTYPE = 'PERS' and FIRST_NAME is not null or SUBTYPE = 'ORG' and FIRST_NAME is null".
Regards,
Marc de Oliveira

Warning icon on Engineer to Relational Model screen

Engineer to Relational Mode l shows warning icon on Attributes, Entities and Logical labels. I don't see the reason.
Do you know what this warning icon is about and how to tackle it?
Thanks,
Prakash

Hi Prakash,
Engineer to Relational Mode l shows warning icon on Attributes, Entities and Logical labels. I don't see the reasonThis mean something is changed. You can click on object and should look at details tab. Entity is composite object and it'll get warning mark also if some of components are changed.
At "compare/copy options" tab you can exclude some properties from compare process if you don't want them to be considered.
Philip

Engineer to Relational Model case sensitive?

I developed my database in the Logical Model using Upper and Lower case. When I`m engineering from Logical to Relational Model, it keeps showing me that all atributes have their names wrong and marks them for change in the relational model. Is there a way to inform data modeler to not consider the change in case as differences?

The thing is that in the Relational Model, all objects are beeing generated in uppercase. When I'm going to update the relational model by enineering from Logical, the program always shows me that the column names are different, when they are not, because the only difference is case! There is already a parameter for the engineering not to test for different case in the entity's name, but no parameter for it in the atribute's name!

SQL Datamodeler 3.0 (Data Modeler 3.0 EA1.)

On the panel 'Structured Types Properties', will be allowed to use a 'Domains' radio button to define the shape of an attribute?
Edited by: user4179829 on Oct 11, 2010 12:24 PM

Scott,
This is one for the feature requests list. You can log requests at sqldeveloper.oracle.com. Please provide a clear explanation of what you request.
Sue

DataModeler: Cannot engineer from logical model to relational model

Hello,
I have been trying for a couple of (very frustrating) hours to engineer a very simple logical model to its relational model. The toolbar button (and also menu option) that should do this just does nothing. No errors, no feedback, absolutely nothing!!! However I could engineer a relational model back to its logical model.
I am using SQL Modeler version 1.5.1 build 525 on Windows Vista. I have closed and restarted the program many times but to no avail. Are there other factors (e.g. anti-virus, JDK etc) that could be responsible? But then why are other parts of the software working but not this one?
Please kindly send your advice asap so I can proceed. I really like the Modeler and will not want to discard it.
Thanks,
Chiedu

Hi Folks,
I was able to figure out the likely cause of the problem. The version of Modeler (datamodeling-1.5.1-525-no-jre.zip) I used was downloaded without JRE. The current version of JRE installed on my computer is Java 6 Update 12 (build 1.6.0_12-b04). I suppose the two don't quite work very well together.
I have now downloaded and installed another version (datamodeling-1.5.1-525.zip) with its own JRE and the problem was resolved.
My guess is that the problem was due to the incompatibilities that may exist between Data Modeler and the various versions of JRE.
Thanks.

[BUG][4.0EA3] Invalid surrogate key is created after engineering to relation model

Repro steps:
Go to Tools -> Domain Administration. Add new domain named MyIdentifier with logical type UNIQUEIDENTIFIER. Apply and save changes.
Go to Tools -> Preferences, then Data Modeler -> Model -> Relational. Get to Surrogate Column Data Type group box and set Domain = MyIdentifier. Apply changes.
Create new Entity and enable option "Create Surrogate Key". Apply changes.
Engineer to Relational Model with default settings.
Expected result:
Entity_1_ID column's data type is UNIQUEIDENTIFIER
Actual result:
Entity_1_ID column's data type is CHAR

I've forgot to mention, that my default RDBMS Site is set to SQL Server 2008. In Types Administration UNIQUEIDENTIFIER is mapped to CHAR for Oracle, but it mapped to UNIQUEIDENTIFIER for SQL Server 2008.

Fwd engineering entity name changes to relational model?

I changed an entity name in my logical model after generating a relational model. But, I cannot figure out how to have SDDM (3.0.0.665) propagate this change to the relational model.
In the Engineer To Relational Model screen, if I select the changed entity from the tree view, in the Details pane there is a "Selected" check box next to the Name property (this line shows the discrepancy between logical name and relational name) but I can't check it. Under the Compare/Copy Options tab in that same dialog, the check box next to Name is checked. But, when I forward engineer the name is not changed.

BTW I just noticed that if I enable "Name Translation" then it seems to work. This is not at all intuitive or obvious, nor does it seem to be explained in the documentation.
According to the help:
Apply Name Translation: Controls whether formal names are translated to abbreviated names when the logical model is forward engineered to a relational model, and whether abbreviated names are translated to format names when a relational model is reverse engineered to the logical model. Name translation is applied only for valid names. In addition, translations between the words entity/attribute/key and table/column/index are performed.

Engineering from relational model to logical model duplicated views

Hi all,
Several times, also in different projects, when I engineer from relational model to the logical model, the comparator tool show me de differences.
In these differences there are no view differences, but when I finish the process everything goes right except that in the logical model under views, I see all the views duplicated with [view_name]v1.
I've tried not selecting the view checkbox, in the compare dialog,but I get duplicated views also.
I don't know fir sue if this happens with table also.
What can I do to solve this problem? Is this a bug?
Edited by: morfeo8marc on 04-abr-2012 2:02

The problem is fixed in DM 3.1.1.703 and it's published. You can run following script and save design in order to get mappings for views recovered.
Philip
lmodel = model.getDesign().getLogicalDesign();
rmodels = model.getDesign().getRelationalDesigns().toArray();
for (var i = 0; i < rmodels.length; i++) {
rm = rmodels;
eviews = lmodel.getEntityViewSet().toArray();
for (var k = 0; k < eviews.length; k++) {
ev = eviews[k];
tv = rm.getTableViewSet().getObjectByID(ev.getGeneratorID());
if(tv == null){
tv = rm.getTableViewSet().getObjectGeneratedBy(ev);
if(tv != null){
rm.getRMExtendedMap().createMapping(ev,tv);

Sql datamodeler: Engineer to relational model

Similar Messages

Maybe you are looking for