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

Similar Messages

  • 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 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();
    - 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();

  • 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!

    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:
         "VALUE" VARCHAR2(255 CHAR),
         PRIMARY KEY ("ID")
         PRIMARY KEY ("ID")
         "ALT_ID" VARCHAR2(255 CHAR),
         PRIMARY KEY ("ID")
         CONSTRAINT "FK6DF8294F2288190D" FOREIGN KEY ("ALT_ID")
    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.

  • 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

    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).

  • 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.

  • 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...
    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.

  • 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:
         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

  • SQL Developer Data Modeler - Relation to Foreign Key Generation

    SQL Developer Data Modeler 2.0.0 Build 584.
    I am having trouble with Relations to Foreign Keys when Forward Engineering a Relational Model from a Logical Model.
    First of all, the Naming Standard is not applied to the Foreign Keys when I perform the Engineer to Relational Model.
    So I right click on the Relational Model from the Browser and Apply Naming Standards to Keys and Constraints.
    I uncheck everything but Foreign Keys.
    Now, Foreign Keys are named according to my Naming Standards.
    However, this process also performs renames on the Column Foreign Keys even though I specifically unchecked that option.
    This appears to be a BUG in the software and I haven't found a way around it.
    I tried using {column} instead of {ref column} in the Naming Standard Template for Column Foreign Key, but that simply resulted in renaming my columns to "{column}".
    Please confirm and/or let me know of any work-around for this.

    Hi Philip,
    Thanks for the reply.
    Is this recorded as a bug to be addressed in the future?
    Should I submit this problem via Oracle Support?
    The other work-around I came up with is to override every Relation name in the Logical Model with the name I want to use in the Relational Model.
    When the Relational Model is Engineered, this becomes my Foreign Key name.
    Of course, this is not how I want to do things, so I am hoping for a bug fix someday.

  • Import / Export MySQL database in SQL Developer Data Modeler

    I have version of SQL Developer Data Modeler and version 3.2.09 of SQL Developer installed.
    When I´m adding a new connection in SQL Developer, I can choose the MySQL tab an create a connection to a MySQL database.
    The connection test was successful and I can see all tables.
    I use the same JDBC driver for SQL Developer and SQL Developer Data Modeler (mysql-connector-java-5.0.4-bin.jar).
    But there are two problems.
    1. First there is an problem when I want to import from a MySQL database (SQL Developer -> File -> DataModeler -> Import -> DataDictionary).
    After choosing the MySQL connection and pressing the next button an error occurs: CONNECTION_TYPE
    What is the reason?
    2. In SQL Developer Data Modeler I have not the CONNECTION_TYPE problem. But when I want to export DDL, there is no MySQL type selectable, although there is working connection to the MySQL Database. It´s the same in SQL Developer.
    What is the reason?

    Data Modeler does not explicitly support import from MySQL databases, although you can use a JDBC connection to do this.
    Philip described how to set this up in forum message How to connect mySQL for reverve engineering
    There is no MySQL tab in Data Modeler - you should use "JDBC-ODBC Bridge" - "other third party Driver".
    Set URL like : jdbc:mysql://localhost:3306/database_name
    driver Class: com.mysql.jdbc.DriverAlso Data Modeler does not support generation of DDL for MySQL.

  • Does SQL Developer Data Modeler fit-in??

    Hi Everyone,
    Wish you happy new year 2011.
    Does SQL Developer Data Modeler support conceptual, logical and physical in our modeling or only logical and physical?
    We all use Erwin for modeling. Erwin works without database repository storing models in desktop folders and provide additional reporting. I find some place SQL Developer Data Modeler talked about repository need.
    Does SQL Developer Data Modeler store the models in local/network folders instead of Database server?
    What are the functions need database based repository to work with SQL Developer Data Modeler?
    We are thinking of using SQL Developer Data Modeler for our conceptual, Logical, and data dictionary need. Will it help in our need?
    Do we need to face any surprises on using SQL Developer Data Modeler for our need?
    Thanks in sharing your experience and helping me out.

    1) Do we need to have Oracle database at back end to work with SQL Developer Data Modeler?No, Data Modeler use Oracle database only if you create reporting repository.
    Data Modeler is free, you need database license only if you want to log service request
    2) Will SQL Developer Data Modeler create any tables (as backend repository ) in Oracle database to store Model details? no
    3) Do we need to create reporting schema in backend oracle database to generate reports of SQL Developer Data Modeler's items such as Entity/attributes etc?no, reports can be created out of current loaded design. However having reporting repository will give you additional benefits - history (reports can be generated for every snapshot of your designs there) and multi-user usage, you can create your own reports
    4) Do we to use SQL Developer Data Modeler reverse engineer from DB2, SqlServer, Terra data etc?Data Modeler has full support for Oracle, DB2/390, DB2/UDB(LUW) and MS SQL Server. Reverse engineering from other databases (including Terra Data) is at generic JDBC level - you'll get some and some will be missing (no check constraints for example).
    You can read release notes http://www.oracle.com/technetwork/developer-tools/datamodeler/ea2-releasenotes-185793.html

  • SQL Developer Data Modeler - integration with subversion

    I just discovered the release of SQL Developer Data modeler, and found this to be very interesting.
    We are still using Oracle Designer for database design, but we are looking for a replacement (for several reasons).
    My question is quite simple:
    Given that the modeler uses a filebased repository, and also given that we have several developers potentially working on a data-model at the same time, how does Data Modeler integrate with subversion for source control etc.?
    Can the repository itself be under source control, and checked in/out directly from Data Modeler?
    Or will only the output files be candidates for version/source control?
    Let me admit right away that I have not read much of the data modeler docs, and I have also not downloaded/installed it (yet), but does anyone have pointers to docs on this , or general input/knowledge around it.
    On a side note, I must say that it puzzles me that a company like Oracle, that delivers one of the best databases doesn't use its database engine to host the repository, but instead chooses to go for files (I assume xml) "scattered all over the place"....
    Well, I guess they a have a reason for it..
    Sql Developer Data Modeler and Subversion anyone?

    Hi Jens,
    It's early days and the initial implementation is indeed file based. Though I'd say not xml files "all over the place", but in ordered folders. Yes, as a database company it does make sense that we'd have a repository for managing and versioning metadata. However the tool supports Oracle and other databases and many companies use open source version control tools, such as Subversion and so anyone using the Data Modeler today can use it with Subversion regardless of the database they are designing for.
    We do plan to have a repository, but in the 6+ months of the early adopter program found that many of the early adopters were happy to place the files under source code control using Subversion and in so doing also managed the multi-user development.
    Integrated Subversion support is planned for a future release.

  • Best book or online education on SQL developer data modeler 3.0 version

    i dont see any OBE for sql developer data modeler the way we have for sql developer, would one of you please suggest the Best book that explains everything about data modeler tool or any other online tutorial for that matter, I am new to this URL and been asked to work on ER (Logical), relational, physical models extensvily.. right away, i will have to build or starts righht from ER/logica and ahead or reverse, forward enginerring. thanks for help friends.

    Did you look at Data Modeler web page.
    There are some online demos and documentation.
    Ivan Zahariev

  • Foreign key Mapping based on Data - in SQL Developer Data modeler

    Do SQL Developer Data modeler supports Foreign Key mapping based on the Data in the Schema rather defined at the DDL ? For e.g if we implement a Objects Relation ship mapping in Data base, we don't define Foreign keys at table creation.
    Toad does this feature through "AUTOMATIC FOREIGN KEYS MAPPING IN TOAD DATA MODELER" more info at (http://toadworld.com/Blogs/tabid/67/EntryId/905/Automatic-Foreign-Keys-Mapping-in-Toad-Data-Modeler.aspx)
    any one know how to implement through some scripts also helps me

    If you have table PKs defined and the candidate columns match those PK columns, then you can use the Discover Foreign Keys utility. Right mouse over the relational model name (node) in the left browser. It is about half way down the menu. I did a blog post about it last week on kentgraziano.com.

Maybe you are looking for