Relational Model - display (FK) next to column

Hi,
I reverse engineered my model from the data dictionary. My model has foreign keys. Similar to Erwin, how can I get data modeler to display that the column is a FK? For example
see the link below
dept_id (FK)
http://content.answcdn.com/main/content/img/CDE/ERWIN.GIF
Thanks

I have the P, U, and * but no F. Although I have FK constraints in my DDL. As:
create table contact
(id int not null,
name varchar2(99) not null,
type int not null,
email varchar2(99) not null,
phone varchar2(99),
description varchar2(256),
date_created date not null,
CONSTRAINT pk_contact_id PRIMARY KEY (id),
CONSTRAINT fk_contact_contacttypeid FOREIGN KEY (id) REFERENCES contact_type,
CONSTRAINT uk_contact_nametype unique (name, type));

Similar Messages

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?

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

Display extra information in entity header of the relational model

Hi,
Is there a way to display extra information in the header of the entity, next to the table name.
Ex : each table in my model has a distinct object id. Right now I enter this info in the Dynamic Properties (Name = OBJECTID Value = 710). It would be really practical for me if that OBJECTID would appear in the relational model diagram.
Thanks.

No, it's not possible
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

It's adding same column to relational model over and over

I'm using 3.3.0.747 now, and I'm pretty sure that it wasn't doing this when I was using 3.1.4. I go into the logical model and add an attribute (say "My notes") to an existing entity (say "Specifications"), adding a preferred abbreviation of "notes" to it. I engineer to the logical model, and it dutifully says that it's going to add a column to the corresponding table ("specs"). And it does.
Now, later, I add some attributes to some other table. When I do the engineering, it says that "notes" doesn't exist in "specs" and it's going to add it. If I let the engineering go through, I find that the relational model for "specs" now has two columns on it, "notes" and "notes1". If I do it again, I get "notes2". If I delete "notes1" and "notes2" and engineer again, "notes1" comes back.
I'm not finding that it does it this every time, but it's doing it for maybe half the columns I add to existing tables. (I haven't figured out a pattern.) If it happens to be a foreign key relationship, it creates an additional foreign key.
So far I've just added a step to my process to hunt down the new columns and delete them (or flag the logical model to not engineer the table at all if I know I haven't changed anything), but there must be something obvious I'm missing..
Edited by: dbomp on Apr 17, 2013 10:53 AM
I'll take back one thing I said: If the once-new column is related to a foreign key, it does keep re-creating the column, but it doesn't create new foreign key relationships to go with it.

I figured it out so I thought I'd put this here in case others bump into it.
What's going on is that the logical-to-relational engineering comparison tool doesn't recognize relational columns that the engineering tool didn't create. Sometimes I would add columns to both the logical and relational models manually rather than engineering. Say all I wanted to do was to add an active_flag to a table. I'd add it to the relational model and then add it to the logical model's corresponding entity with exactly the same values. Later, when I had a bunch of logical model changes to engineer, it wouldn't recognize the active_flag ("preferred abbreviation") in the entity as being the same thing as the active_flag in the relational table, and it'd create an active_flag2 column.
Lesson: only create new relational table columns by engineering them from the logical model.

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? :-/

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.

How can i import tables from a different schema into the existing relational model... to add these tables in the existing model? plss help

how can i import tables from a different schema into the existing relational model... to add these tables in the existing relational/logical model? plss help
note; I already have the relational/logical model ready from one schema... and I need to add few more tables to this relational/logical model
can I import the same way as I did previously??
but even if I do the same how can I add it in the model?? as the logical model has already been engineered..
please help ...
thanks

Hi,
Before you start, you should probably take a backup copy of your design (the .dmd file and associated folder), in case the update does not work out as you had hoped.
You need to use Import > Data Dictionary again, to start the Data Dictionary Import Wizard.
In step 1 use a suitable database connection that can access the relevant table definitions.
In step 2 select the schema (or schemas) to import. The "Import to" field in the lower left part of the main panel allows you to select which existing Relational Model to import into (or to specify that a new Relational Model is to be created).
In step 3 select the tables to import. (Note that if there are an Foreign Key constraints between the new tables and any tables you had previously imported, you should also include the previous tables, otherwise the Foreign Key constraints will not be imported.)
After the import itself has completed, the "Compare Models" dialog is displayed. This shows the differences between the model being imported and the previous state of the model, and allows you to select which changes are to be applied.
Just selecting the Merge button should apply all the additions and changes in the new import.
Having updated your Relational Model, you can then update your Logical Model. To do this you repeat the "Engineer to Logical Model". This displays the "Engineer to Logical Model" dialog, which shows the changes which will be applied to the Logical Model, and allows you to select which changes are to be applied.
Just selecting the Engineer button should apply all the additions and changes.
I hope this helps you achieve what you want.
David

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

Relational Models Sequence Order

Is there any way to amend the display order of relational models that are listed under the 'Relational Models' node? - a sequence attribute would be nice.

a sequence attribute would be niceMay be order by name will be enough.
Philip

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

DM3.0 EA2: Arcs do not engineer correctly to relational model

It seems to me that an arc between two mandatory relations in the logical model are engineered into two mandatory foreign keys in the relational model. This is clearly not the purpose of an arc.
What is even worse is that it seems that it is not possible to change the foreign keys into being optional. Both the foreign key columns and the foreign keys themselves are mandatory with a read only property that cannot be changed.
- Marc de Oliveira

I logged bug for that.
Philip

Engineering logical subtypes to Relational model

I have a logical model with subtype (box in box). When I forward engineer to a relational model there is nothing in the model to represent the subtypes. I was expecting (as in old Designer) to see a differentiator "type" column to be generated with a column check constraint based on my subtypes. In the logical model I selected "single table" as the implementation strategy.
Note I also have these entities tagged as Dimensions and did notice the engineering dialog showed the substypes as hierarchies too.
Am I missing a a preference setting somewhere?

Hi Kent,
I was expecting (as in old Designer) to see a differentiator "type" column to be generated support for that will be added later.
Note I also have these entities tagged as Dimensionswhat do you expect - if you change implementation from "single table" to something else you'll get tables also classified as dimension, no other magic will be involved
and did notice the engineering dialog showed the substypes as hierarchies tooI don't see your point here.
Philip

Engineer between Logical Model and Relational Model

I am trying to update changes from one model to the other but there are dublicate entries generated instead of updates.
The Logical Model was imported from Oracle Designer, the Relational Model was imported from data dictionary.
Our rule is, that the name of Entities/Tables and Attribute/Columns are identical.
So I changed the Naming Standard of the Logical Model in Preferences
from Separator = Space to Separator = Character with char = Underline.
If the entity is not existing, it is created with the correct name.
If the entity exists, a new entity is created with Namev1.
The same happens when I try to update changes in the other direction.
How can I achieve that the existing entity (or table) is updated and not a new one is created?
Or in other words, is there a way to link entities to corresponding tables?
Walter

Hi Walter,
The Logical Model was imported from Oracle Designer, the Relational Model was imported from data dictionaryit's good to import entities and related tables from Designer repository together. Data Modeler will import the link between them and use that link in synchronization between logical and relational model. After that you can import details for physical model from database.
If you don't have tables in Designer repository and keep the same names for entities, attributes, tables and columns then you can engineer logical model to relational and import details from database.
Philip

Relational Model - display (FK) next to column

Similar Messages

Maybe you are looking for