Sql Developer Data Modeler 3.0 EA1: Relationship source and target names

When opening my version 2 model in version 3.0 EA1 the source name and target name of all my 231 relationships are deleted.
Is there a solution for this? I don't want to reenter these 462 labels...
Sincerely,
Marc de Oliveira

Hi Peter,
When I examine an XML file for a relation converted from version 2.0, the XML elements "nameOnSource" and "nameOnTarget" are missing in the converted 3.0 EA1 versionthey are not loaded during "open" of older design. If you define them they will go into XML file.
Philip

Similar Messages

Sql Developer Data Modeler 3.0 EA1: Custom transformation script

What is the object model used by:
Tools -> Design Rules -> Transformations
From looking at the examples (and guessing) I have managed to create ID attributes on all my entities, but how do I set its sequence number or set it as the primary key?
entities = model.getEntitySet().toArray();
for (var e = 0; e<entities.length; e++)
entity = entities[e];
att = entity.createAttribute();
att.setName('ID');
- Marc de Oliveira

content of XML files:
1) class described, parent class if there is one
2)<property .../>
describes property - set and get method, data type of property, default value
3) <collection ... />
describes collection of objects belonging to class - 5 collections are defined in Table.xml - columns, indexes, table check constraints, column groups and spatial definitions
- get method - to get collection
- create item method - method of described class used to create item for that collection; so for columns collection table.createColumn() will create column in table
- other methods - add, move, remove if are defined
4)other meta data
definitions in 1) .. 4) are used by Oracle SQL Developer Data Modeler, so it'll be wrong to modify those xml files
5)<roproperty ../>
Data Modeler doesn't parse/process these definitions, we decided to not filter them out however you should not rely that much on them
6)some junk left
For each object you can set your own properties and they will be persisted (also included in compare/merge in versioning) together with other information for object - look at "template table" example in transformation scripts. Here are methods you can use:
void setProperty(String key, String value);
     String getProperty(String key);
     boolean hasProperty(String key);
     boolean hasProperty(String key, String value);
     void removeProperty(String key);
     void clearProperties();
     Iterator getPropertyNames();
Philip

Sql Developer Data Modeler 3.0 EA1: Auto route off

I admire that the data modeler tries to automatically position relationships and data flows. I am sure it is very hard to automate and I don't think it works very well in this tool.
So, I am happy that you have the option of turning "auto route" off as I am quite particular about how diagrams should look.
In the EA1 it seems that even with "auto route" turned of, all connected relationships and dataflows are automatically repositioned as soon as an entity or process box is resized or moved - even the tiniest bit.
I think the tool should not reposition relationships or dataflows as long as their current position can be maintained after the connected entity/process is resized or moved. When lines have to be moved the tool should try to maintain a position as close to its original position as possible.
Let me know if there is a way to achieve this.
Also, when relationships or dataflows have to be repositioned by the tool, I think they should be placed as far away from each other as possible (giving more room for labels). Currently, it seems that the default behavior is to lump relationships and dataflows close together when they connect the same entities or processes.
/ Marc de Oliveira

it's the same in Data modeler v. 2.0No, in version 2.0 it is not the same. The line stays in place if you move the entity or process in the same direction as the line, eg a vertical line is not repositioned if you move a connected entity or process vertically. The same goes for horizontal lines.
Also, when resizing the right side or the bottom side of an entity or process, lines connected to it are not repositioned (as long as the box does not become too small).
You can get lines "more" fixed if you introduce intermediate point Intermediate point? I never heard of that. Where do I learn more about that? I could not find it in the help file.
/ Marc de Oliveira

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

Sql Developer Data Modeler 3.0 EA1: Export - To reporting schema

When launching Export -> To reporting schema the schema tables are created and messages show that data is being generated but after indicating that it "Exporting Diagrams" I get the following error message:
"Error occurred while exporting to Reporting Schema. See the log file for details."
and all the tables are left empty.
The message log is not indicating that anything went wrong.
What could be the problem?
- Marc

This is probably what you are looking for:
2010-10-14 14:56:43,680 [Thread-11] ERROR ReportsHandler - Error Exporting to Reporting Schema:
java.lang.NullPointerException
     at oracle.dbtools.crest.model.design.DesignPart.doSetMainViewVisible(Unknown Source)
     at oracle.dbtools.crest.model.design.DesignPart.setMainViewVisible(Unknown Source)
     at oracle.dbtools.crest.model.design.DesignPart.setMainViewVisible(Unknown Source)
     at oracle.dbtools.crest.exports.reports.RSDiagrams.ensureMainViewVisible(Unknown Source)
     at oracle.dbtools.crest.exports.reports.RSDiagrams.export(Unknown Source)
     at oracle.dbtools.crest.exports.reports.ReportsHandler.export(Unknown Source)
     at oracle.dbtools.crest.swingui.ControllerApplication$ExportToReportsSchema$1.run(Unknown Source)
What does it mean?
/ Marc de Oliveira

Tables in SQL DEVELOPER DATA MODELER seem to be read only and have a chain symbol in the upper left

I have a bunch of tables in my data model. I have three relational models defined in this file. In one of the models, all the tables seem to be read only. They all have a chain in the upper left hand corner of their box.
I am not using version control, so that are not checked in or anything like that.
How do I unlock these objects? Why to they appear to be locked?
Thanks

It looks like you've linked tables across multiple models or designs.
Does this look about right?

Sql Developer Data Modeler 3.0 EA1: Engineering relationships to relational

When doing 'engineer to relational model' the relationship names are converted directly to foreign key names.
So, when the relationship between EMPLOYEE and DEPARTMENT is called 'working in' then the generated foreign key is also called 'working in' (not event 'working_in').
Is it possible to have it engineered to something like 'employee_working_in_department_fk'?
- Marc de Oliveira

Obviously, a property called "Plural" and an option for engineering using "Plural" names instead of entity names.
This would also allow us to have a nice relationship report where we could translate relationships into natural languages, like this:
Each DEPARTMENT may be employing one or more EMPLOYEES.
/ Marc

SQL Developer Data Modeler- Creating super/subtype relationship

The User's Guide does not tell you how to create super/subtype relationship.
To create super/subtype relationship in a logical model, you must already have the two candidate entities; one to be the supertype, the other subtype.
- on the logical model diagram, right click the candidate subtype and select Properties
- on the Entity Properties dialog box, select the candidate supertype from the Super Entity drop-down list, then OK
Depending on whether you enable or disable the Box-in-box Presentation on your logical diagram, the subtype would be shown inside or outside its supertype entity, respectively

Hi Peter,
When I examine an XML file for a relation converted from version 2.0, the XML elements "nameOnSource" and "nameOnTarget" are missing in the converted 3.0 EA1 versionthey are not loaded during "open" of older design. If you define them they will go into XML file.
Philip

Sql Developer Data Modeler 3.0 EA1: Process order/number

When opening my version 2.0 model in version 3.0 EA1, the process numbers are as I originally saved them.
After saving the model as a version 3.0 model (using "Save as..."), when I reopen that version all processes have been reordered on all levels of my model (about 300 processes).
Actually, it looks like 1 becomes 4, 1.1 becomes 4.4, 1.1.1 becomes 4.4.4 etc...
Strange behavior. Is there any way to avoid this?
/Marc de Oliveira

Hi Mark,
thanks for feedback. I logged bug for that.
Is there any way to avoid this?No for EA1 release.
Philip

Sql Developer Data Modeler 3.0 EA1: Engineering singular to plural

Do you have a strategy for how I engineer all my singular entity names (such as EMPLOYEE) into plural table names (such as EMPLOYEES)?
- Marc de Oliveira

Obviously, a property called "Plural" and an option for engineering using "Plural" names instead of entity names.
This would also allow us to have a nice relationship report where we could translate relationships into natural languages, like this:
Each DEPARTMENT may be employing one or more EMPLOYEES.
/ Marc

SQL Developer Data Modeling pricing

I just downloaded the EA version of SQL Developer Data Modeling. I read in the release notes that the production release won't be free - any idea about the pricing ?
Matthias

Once the pricing for SQL Developer Data Modeling has been confirmed, we will release the full licensing detail. This will not affect the SQL Developer licensing that exists today. We plan to release SQL Developer Data Modeling as a stand alone product and then as an extension to SQL Developer, for those who want to work in an integrated environment. You can download the second early adopter release of SQL Developer Data Modeling and test and use the product. Once we have a production release, we will not answer queries on the early adopter releases and the feedback application we are currently offering for this will be shut down. As such you can continue to work with the early adopter release, but it is incomplete and would be unsupported.
Sue

SQL Developer Data Modeler not drawing foreign key relationships

I'm having trouble with SQL Developer Data Modeler when I importa a DDL that has foreign keys. I export DDL files from SQL developer and choose various subsets of files. Sometimes Data Modeler will not recognize a foreign key if I include say a dozen files in the DDL file, but it will if I include just a few. Worse, even if the foreign key is recognized, sometimes it is not drawn in the Data Modeler and I have no way to make it be drawn. To be specific, I import a file containing the DDL for just two tables -- I see the foreign key! I import a file containing the DDL for a dozen tables including the two, I don't! Is there something I am not understanding about when Data Modeler will draw foreign keys or is the tool simply quite buggy?
Much thanks!
-ttamon

Hi Philip,
I believe I have isolated the problem. Apparently if a field is named "FOREIGN..." it interferes with the tool recognizing foreign keys. Try to import a DDL file containing the following text:
CREATE TABLE "SAMPLE"."SAMPLE_ONE"
(     "ID" VARCHAR2(255 CHAR) NOT NULL ENABLE,
     "VALUE" VARCHAR2(255 CHAR),
     PRIMARY KEY ("ID")
TABLESPACE "SAMPLE_DATA" ;
CREATE TABLE "SAMPLE"."SAMPLE_TWO"
(     "ID" VARCHAR2(255 CHAR) NOT NULL ENABLE,
     "FOREIGN_NAME" VARCHAR2(255 CHAR),
     PRIMARY KEY ("ID")
TABLESPACE "SAMPLE_DATA" ;
CREATE TABLE "SAMPLE"."SAMPLE_THREE"
(     "ID" VARCHAR2(255 CHAR) NOT NULL ENABLE,
     "VALUE" VARCHAR2(255 CHAR) NOT NULL ENABLE,
     "ALT_ID" VARCHAR2(255 CHAR),
     PRIMARY KEY ("ID")
TABLESPACE "SAMPLE_DATA" ENABLE,
     CONSTRAINT "FK6DF8294F2288190D" FOREIGN KEY ("ALT_ID")
     REFERENCES "SAMPLE"."SAMPLE_ONE" ("ID") ENABLE
TABLESPACE "SAMPLE_DATA" ;
You will discover the foreign key is not recognized or drawn! Now, if you swap the location of the third table (put it up first) everything works fine. This is how I discovered the problem, various subsets would work, others would not. To confirm the problem is with the field named "FOREIGN_NAME" use the DDL as specified above but change the first letter in the word "FOREIGN" to something else, and it will recognize the foreign key. Looks like a bug to me (took me about 4 hours to isolate this!). I am using Oracle SQL Developer Data Modeler version 2.0.0 Build 584.
-ttamon

SQL Developer Data Modeler: Logical model, unable to create arc

I have a logical model in SQL Developer Data Modeler. Entity A has two 'incoming' foreign key relations to entities B and C. Both releations have the same optionality and cardinality. I want to place both relations in an arc. I see the buttons in my toolbar menu, but they are not enabled. Even when I select both relations it is not.
Bringing the logical model to the relational model creates foreign keys. These foreign keys can be selected and when I do that the 'Create new arc' button in the relational model toolbar is enabled.
What am I missing in the logical model ...? The documentation doesn't give a clue.
Erik

Thanks Sue, that worked. It is different from the way the ERD in Designer worked. Is there any reasoning behind it. As far as I know you should only put into an arc two or more relationships pointing to the same entity with the same optionality and the same cardinality. Selecting the entity with the relationships can only help in identifying at which relationship end the arc should be created but that is obvious.
And asking the question is answering it: it will help in adding an arc to two or more entities originating and ending at the same entity (and same cardinality and optionality).
Is that the reasoning behind it?
Regards
Erik

SQL Developer Data Modeler - Limits

Hi Everybody,
I am looking for SQL Developer Data Modeler limitations such as on entities, relationships, sub-types etc.
Is it documented anywhere?
Are we able to build data models with 150+ entities and associated relationships with SQL Developer Data Modeler?
Thanks in sharing your experience.

We have teams in Oracle and customers who are build models with well over 1000 entities and all the relationships involved with that scale. The tool is designed and positioned as an enterprise tool and as such handles large scale models.
Sue Harper

Oracle sql developer Data Modeler -er diagram

Hi
I tried to Oracle sql developer data modeler for show relational ER diagrams.
Tables are came on data modeler but not shown relations between tables.
like this
How can show relations between tables?
http://i54.tinypic.com/30wxq1e.jpg

SDDM cannot create an ER diagram with only simple table definitions. It requires that primary keys (PKs) and foreign keys (FKs) be defined first. My guess is you imported these table designs from an existing database. If so, that database does not contain those constraints. (I have found this to be an issue in many organizations over the last 20 years - including my current job). You will have to determine:
1. The PKs for each table (either via data profiling or talk to someone who "knows" what they are supposed to be, or by reading application logic/code used to manage the tables).
2. The FKs between the tables. You may be able to guess some of that based on column names, otherwise you will have to figure them out (same as above)
Then you can update the model in SDDM with the PK definiions (manually). You must do that first before you draw in the FKs between the tables. Now if you want a true Entity Relationship model you need create a logical model from this relational model. The SDDM utility for that will convert the tables to entities and the FKs to relationships.
I have the basic steps with screen shots outlined in a presentation I gave in Denver in late 2009. It was an earlier version of SDDM but the basics are the same. You can find the presentation is here: http://www.rmoug.org/QEW2009/SQL%20Developer%20Data%20Modeler%20(2).pdf. Start at about slide 12.
HTH
(FYI - I no longer work at that company so the contact information not correct anymore).
Edited by: Kent Graziano on Apr 25, 2011 1:13 PM
Edited by: Kent Graziano on Apr 25, 2011 1:14 PM

Sql Developer Data Modeler 3.0 EA1: Relationship source and target names

Similar Messages

Maybe you are looking for