Define fields names in relation at logical model

Hi all,
Image
On a Logical Model, I have 2 entitys, Events and Menu, and has 2 relations.
When Engineer to Relational, creates 2 new fields in my Events Table, Menu_ID, Menu_ID1. There are some way, in the relation at logical model, to specify the names of the final fields, to avoid to change it later at relational model?
Regards.

Hi,
you can look here Role Naming Foreign Key columns
Philip

Similar Messages

Option Show Source/Target Name "on" in the logic model

In the data modeler 2.0.0 was the option Show Source/Target Name “on”. Where do I find it in data modeler 3.0.0 ?

Hi,
Right click on Logical diagram and from context menu select Show->Labels
Regards,
Ivan Zahariev

Help: User defined field name to change

All Prof, please help me on this.
I am trying to change the name of "2nd ship date" under A/R sales -> A/R invoice to "BL Date". I can change the show column name, but cannot change the label of the input box.
2nd ship date: _______(input box)
2nd ship date --> BL Date

If you refer to the query parameter, that would not be changeable. System will only show the internal name.
Thanks,
Gordon

How to change "Relation UID" attribute name in logical model?

Beginner question here, sorry if it has been covered already.
In the Logical model in Data Modeler, how do I change an attribute name which is used as a "Relation UID"?
For example, I create two entities each with a Primary UID called "id", then create a 1:1 relationship. Each entity will now have an attribute called "id1" marked as a Relation UID, but I can find no way to change the attribute's name. Is there a way?
Thanks.

Hi GuyM,
you need to check setting in preferences - "Data Modeler>Model>logical" - FK attribute name synchronization - clear the check box if you want to set the name manually.
Philip

How to copy field comments from logical model to relational one?

Dear gurus!
I had a logical model without field comments. Then I made an engineering of logical model into relational one. Later I added field comments to logical model. How can I copy these values to relational model? Seems to me that when I use
model.getTableSet().toArray()
then I get list of relational model tables. How can I get a list of logical "tables" and to get a relations between those two lists?
Thank you!
Edited by: user12947051 on 12.01.2012 23:58
Edited by: user12947051 on 12.01.2012 23:58

You don't need to write and run script for that. Just use engineering to relational model. Use compare/copy options tab if you don't want something else to go into relational model
Philip

Bug regarding not filling in length of varchar field in logical model?

I successfully was able to create a logical model, engineer to relational, and generate DDL from this.
However, I found after generating the DDL and attempting to run it, I received errors in creation of some tables saying "missing left parentheses."
After going back and checking, it turned out that I was somehow able to define columns of type varchar in the logical model without putting in a length for the column. Data Modeler generated the DDL for the table looking something like this:
CREATE TABLE LIC_TYPE
    ID     INTEGER NOT NULL ,
    CODE   VARCHAR2 (1024 BYTE) NOT NULL ,
    "DESC" VARCHAR2
LOGGING ;
(for the DESC column) -- which then throws an error.
Should DDL generation should throw a warning when attempting to create CHAR or VARCHAR columns without a length instead of generating the DDL with no errors? Or is this intended functionality?
Using SQL Data Modeler/SQL Developer 4.1 EA2.

Hi,
Thanks for reporting this problem. I've logged an enhancement request.
David

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

DM3.0 EA2: Logical Model Relation Cardinality:Source Optional mislabeled?

In logical model, created a 1:N non-identifying relation between 2 entities - Parent and Child. Parent is 1:N with Child. Both entities have a single column primary key - parent_id and child_id respectively. I would like to enforce RI such that a parent may exist with no children, but a child may not exist without a parent.
In the logical model the relation properties, cardinality - I modify the Source Optional and Target Optional checkboxes to achieve my desired result. I first tried checking Target Optional and leaving Source Optional un-checked. I then engineer a physical model and generate DDL for Oracle 11g I get this constraint:
SQL>ALTER TABLE child
2      ADD CONSTRAINT Relation_1 FOREIGN KEY
3      (
4       parent_id
5      )
6      REFERENCES parent
7      (
8       parent_id
9      )
10      ON DELETE SET NULL
11 ;
Table altered.Here's a test case illustrating this isn't quite what I wanted (starting with both tables empty):
SQL>
SQL>
SQL>insert into parent (parent_id) values (1);
1 row created.
SQL>commit;
Commit complete.
SQL>
SQL>insert into child (child_id, parent_id) values (901, 1);
1 row created.
SQL>commit;
Commit complete.
SQL>
SQL>delete from parent;
delete from parent
ERROR at line 1:
ORA-01407: cannot update ("ODS_ETL_OWNER"."CHILD"."PARENT_ID") to NULLIf I have Source Optional checked, and Target Optional not checked, engineer a physical model and generate DDL for Oracle 11g I get this constraint which produces the desired results with my test case:
SQL>ALTER TABLE child
2      ADD CONSTRAINT Relation_1 FOREIGN KEY
3      (
4       parent_id
5      )
6      REFERENCES parent
7      (
8       parent_id
9      )
10 ;
Table altered.
SQL>
SQL>insert into parent (parent_id) values (1);
1 row created.
SQL>commit;
Commit complete.
SQL>
SQL>insert into child (child_id, parent_id) values (901, 1);
1 row created.
SQL>commit;
Commit complete.
SQL>
SQL>delete from parent;
delete from parent
ERROR at line 1:
ORA-02292: integrity constraint (ODS_ETL_OWNER.RELATION_1) violated - child
record foundBut that seems backwards - and the documentation also reads as if it’s backwards. Am I missing something or are the Source Optional and Target Optional checkboxes mislabeled? Should they be Source Manditory and Target Manditory?

I would like to enforce RI such that a parent may exist with no children, but a child may not exist without a parent.You need to set parent as optional and child to be mandatory.
Am I missing something or are the Source Optional and Target Optional checkboxes mislabeled? Should they be Source Manditory and Target Manditory?There is a relationship and two ends of that relationship and you can set for each end whether it's optional or not. And that's seen directly using Barker notations. Source and target optionality place will be swapped on diagram if you use IE notation.
I expected that cardinality part could be more confusing for you because at source end you define cardinality of the target, but it seems you have no problem with that.
Philip

Delete Rules between Logical Model and Relational Model are different

Relation Properties in Logical model has three Delete Rules: "RESTRICT", "NO_ACTION", "SET NULL".
1. "RESTRICT" and "NO_ACTION" are same
2. "CASCADE" is missing.
However, Foreign Key Properties in Physical model has three Delete Rules: "RESTRICT", "NO_ACTION", "CASCADE".
1. "RESTRICT" and "NO_ACTION" are same
2. "SET NULL" is missing in this case.
They are supposed to have "NO_ACTION or RESTRICT", "SET NULL", and "CASCADE".
Please fix this ASAP. It is really annoying in Engineering process. Modeler creates duplicate wrong relationships while it engineers.
Thanks.
Edited by: hayangae on Oct 9, 2012 1:01 PM
Edited by: hayangae on Apr 3, 2013 4:08 PM

Hi,
it seems you are not using the latest version 3.3. In earlier versions - delete rule set on relationship was used only in some cases to set delete rule on related foreign key. Now delete rule is transferred to FK as it's defined on relationship.
I assume you are using Oracle database - "Restrict" doesn't appear anymore for Oracle.
2. "SET NULL" is missing in this case.Most likely the foreign key is set as mandatory thus you cannot use "set null" as option.
Modeler creates duplicate wrong relationships while it engineers.Can you elaborate on that - example?
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

Importing multiple column names to Logical Model

I have approximately 2,000 column names to import into a new logical model and create my glossary. The names are in currently in .xls format. Is there an easy/efficient way to do this or must I enter each into the logical model attributes? Maybe a way to cut/paste multiple columns into the logical model?
Thanks...

Hi,
it's not clear what are you trying to achieve:
I have approximately 2,000 column names to import into a new logical model are you trying to create attributes in logical model - you also need entities that will contain these attributes.
and create my glossary. The names are in currently in .xls format.or you want to create glossary from your file. You need to transform your file in following format and import it in glossary editor using ERwin txt format:
COUNTRY,CTRY,
IDENTIFICATION,ID,
REGION,REG,
DEPARTMENT,DEPT,
Maybe a way to cut/paste multiple columns into the logical model?if you have tables with columns in relational model then you can use "Engineer to logical model" functionality to get entities and attributes in logical model.
Philip

Data Modeler 3.0 / Logical Model / Move relationship names

Hi,
When showing relationship names in the logical model they often appear at a not so good place
(eg two labels at the same location, lable over a table name,lable showing nowhere near his relationship line, etc...)
In the former edition, when the model was still saved as a .xml file we had the possibility to 'move' the labels around
and put them at a more proper place and as such create a solid and clear schema.
In the new version (3.0.0....) it is no longer an xml file but a .dmd file that is created and it is no longer posiible to move the labels (relationship names).
They can only be resized...
The loss of this functionality is ..... making me print the schemas whithout displaying the relationship name (if not the outprint is rather messy)
Is there a way to move the labels?
and if not , will it be re-enabled in a next edition?
reards,
E.

Hello!
I have to follow this thread too.
I use SDDM 3.3 EA2
The autorouting of FKs is great and at the same time annoying. Sometimes the endpoints of FK-Lines stick to entities and you can't move them to a correct position.
Sometimes when you position the FK-lines in a desired postion and you resize the subview the autorouting changes them. Very annoying!
Formating notes is possible but when you open the subview again the format is lost.
Positioning self joins is another 'tearing the rest of my hairs'
And you cannot set the width of borders of entities
And I'd like to have the possibiltiy to change or configure at least 2 or all fields of the legend
To offer something positiv. Thank you very much Philip, for adding the possibilty to change the grid size!
Best wishes
Guenter

Logical Model Names

Is there anyway to show logical names in the logical model for the attributes? I can see that you can enter a synonym and it shows that but for the attributes it doesn't seem to be a way to show logical names in the same manner.
Other tools allow you to display business names, not names with underscores, in the logical model. I am looking to do the same thing with Data Modeler. Without this ability, the logical pretty much looks like the physical.

In that case where does the logical name get displayed in the logical model? I suspect the answer is somewhat similar in that you would enter the logical name and then transform to the physical.Correct. Why do you need to use physical names in logical model? You can use preferred abbreviation property in order to override translation with glossary. In this way you can have several relational models with different names in each one. Then you can create physical models and change the names in them depending on implementation specifics.
Philip

How can i get value when the field name is user's defined

Hi,
I have a one java method:
public ResultSet countUserDb(String id) {
ResultSet rs = null;
con = dbcon.connect();
String queryString = ("select count as count from
db_allocation where user_id='"+id+"'");
Statement stmt = con.createStatement();
rs = stmt.executeQuery(queryString);
When i call it in a jsp file.
ResultSet counter =db.countUserDb(request.getParameter("id"));
if(counter.next())
int x=rs.getInt("count");
Tomcat said incorrect column name.How can i get the result set when the field name is user's defined.
Best regards
Ricky

You should give the user defined name in the ResultSet.getXXX method to retrieve the column value.
Example
SQL:
Select ename as employeename from emp;
You should say :
ResultSet.getString("employeename"); to get the value.
Alternatively you can retrieve it using column number:
ResultSet.getString(1);
Chandar

How can i get the value when the field name is user defined

Hi,
I have a one java method:
public ResultSet countUserDb(String id) {
ResultSet rs = null;
con = dbcon.connect();
String queryString = ("select count(*) as count from
db_allocation where user_id='"+id+"'");
Statement stmt = con.createStatement();
rs = stmt.executeQuery(queryString);
When i call it in a jsp file.
ResultSet counter =db.countUserDb(request.getParameter("id"));
if(counter.next())
int x=rs.getInt("count");
Tomcat said incorrect column name.How can i get the result set when the field name is user's defined.
Best regards
Ricky

Hi Ricky
To access pseudo columns you can specify an alias or use the index on the column (e.g. getInt(1)).
Chris
NB: you should use bind variables instead of concatenating the id to the SQL statement.

Define fields names in relation at logical model

Similar Messages

Maybe you are looking for