Unwrapping names of foreign key in relational model

Similar Questions

• Rename the name of foreign key programmatically

  Hello

  I tried to rename a foreign key by program through this code of Rhino:

    var tables = model.getTableSet().toArray();
    for (var tidx = 0; tidx<tables.length;tidx++){
      var table = tables[tidx];
      var keys = table.getKeys();
      var keyCount = keys.length;
      for (var kidx = 0; kidx<keyCount;kidx++){
        var key = keys[kidx];
        if (key.isFK()) {
          var keyName = key.getName();
          if (keyName.endsWith("___FK")) {
            var keyNameLength = keyName.length();
            var newKeyName = keyName.substring(0,keyNameLength - 5) + "_FK";
            key.setName(newKeyName);
            table.setDirty(true);
          }
        }
      }
    }
  
  

  I was expecting to change the name of any foreign key when the name ends in '___FK' and simplify it to "_FK".

  It changes something, as you can see on this picture, but not all:

  

  The green ellipse indicates the place where the replacement has been successful, the reds, the places where the old names of foreign key has not changed.

  I would like to know what to do in my script.

  Thank you in advance,

  Gábor Tóth

  Hello

  Try this one:

  var tables = model.getTableSet () .toArray ();

  for (var tidx = 0; tidx<>

  var table = tables [tidx];

  var keys = table.getFKAssociations ();

  var keyCount = keys.length;

  for (var kidx = 0; kidx<>

  var = key keys [kidx];

  keyName var = key.getName ();

  If (keyName.endsWith ("___FK")) {}

  var keyNameLength = keyName.length ();

  var newKeyName = keyName.substring (0, keyNameLength - 5) + "_FK";

  key.setName (newKeyName);

  table.setDirty (true);

  }

  }

  }

• Entity and attribute transformation of names (case-sensitive) to the relational model

  Hello

  For the names of entities and attributes, I would use camel casing, e. g. AccessRightGroup (or the right access group) and its translation to the relational model in the Table name access_right_groups. I found, I can do in the entity properties > General > abbreviation preferred by writing the name of the table you want in this area. But I guess that there is a more elegant way by setting that breaks are transformed into small capital and underlined and entity (set) becomes plural as table. Is there such a possibility?

  How that would make the camel case attributes?

  Best regards, Robert

  Hi Robert,.

  case-sensitive, you must set 'Title case' as a separator for logic model in the design properties dialog box "settings > naming standards '-c' is for this form of the names AccessRightGroup; for group of access rights that you need not change anything - the default separator is set to 'space '.

  For the plural in the relational model, you need a glossary with defined plurals - however it only works for the entity name unique term. I logged an ER to change this.

  Tiny in a relational model - well you must set to relational model - in the Properties dialog box - "(Naming options > Table, cas de caractères...-mis à baisser et le nom sera mis dans cette affaire àle cours de la transformation) - otherwise you always can use the script provided with Data Modeler to convert the names of all the lower/upper cases."

  Phhilip

• Renaming of the foreign keys in the relational model

  Hello
  
  
  I'm new to the Data Modeler, we use v 3.0.0.66.5 and Oracle 11 g, and I am trying to build a logic and a relational model for a new application.
  
  We always call our primary keys as the ID, this causes me a problem with my names of foreign keys in the relational model, as they show as ID #. Is it possible to add the abbreviated of the table of the foreign key?
  
  Thanks in advance
  
  Sue

  Yes it is.

  Take a look at the tools > preferences, select Data Modeler > naming Standard > model, you can specify the standard you want to use for your foreign key. You can apply this designation to existing models and all new created FK uses the same model. To apply the standard to existing templates, select the relational model in the browser, right-click to display the context menu and select the menu "apply Naming standards... ».

  Sue

• name of the foreign key column

  I'm new to the SQL Developer Data Modeler, I try to use it so that I can recommend to peers.

  in the logic model, I created 2 entities:

  entity: order_headers

  attributes: header_id (primary key), order_number

  entity: order_lines

  attributes: line_id (primary key), item_code

  and then I create a relationship 1: n to order_headers to order_lines

  Now if I find out the attributes of order_lines, there are 3 attributes:

  line_id, item_code and header_id

  I do an "engineer of the relational model

  in the Relational_1, I see that my order_lines table has a field: order_headers_header_id

  How can I configure step 'Engineer to the relational model' to use 'header_id' instead of 'order_headers_header_id '?

  I use Oracle SQL Developer Data model version 4.0.1.836 build 836

  Hello

  You must change the name for "Foreign key column" model in the design properties dialog box - "settings > Naming Standard > models.

  It should be {column Ref} only to get required name.

  Philippe

• FWD entity engineering of relational model name changes?

  I changed a name of entity in my logical model after generating a relational model. But I can't understand how having SDDM (3.0.0.665) to propagate this change to the relational model.
  
  In the screen of the engineer to the relational model, if I select the entity changed tree, in the details pane, there is a checkbox next to the Name property (this line indicates the gap between relational and logical name) "Selected" but I can't check it out. Comparison/copy in this same dialog box Options tab, the checkbox next to name is enabled. But, when I send an engineer the name is not changed.

  After changing the name of the entity, select the relational model engineer
  Down at the bottom, select the tab General options.
  Select apply the translation of names
  Engineer

  Now the name will change in the relational model.
  Michael

• First database with Oracle 12 c and Entity Framework 5: no foreign key in the EMD Associations

  We have an updated database implemented in Oracle 12 c R1. When attempting to reverse engineer the EMD of the DB using Visual Studio 2013 with ODAC 12 c Release 2 and Oracle developer Tools support all we get are entities with no association, despite multiple foreign keys defined in the database. There, of course, no navigation property in both entities. No error or warning messages are displayed and activate us the option "include foreign keys in the model columns.

  Does anyone have any idea why this might happen?

  If you use files PDB (pluggable database), there is a known bug (17474322) to generate an EDM with foreign keys in a PDB file. This is probably the question you are running in.

• find the foreign key data

  Hello
  
  I want to have the details as the tablename, volumn name of foreign key to a table of reference.
  

  SELECT a.column_name,  
          c_pk.table_name r_table_name, c_pk.constraint_name r_pk
    FROM all_cons_columns a
    JOIN all_constraints c ON a.owner = c.owner
                          AND a.constraint_name = c.constraint_name
    JOIN all_constraints c_pk ON c.r_owner = c_pk.owner
                             AND c.r_constraint_name = c_pk.constraint_name
   WHERE c.constraint_type = 'R'
     AND a.table_name = :TableName

  Using this query, I get everything except the column name for reference.
  
  Can someone please help?
  
  Thanx

  You must add another join to ALL_CONS_COLUMNS:

  SELECT a.column_name,
          c_pk.table_name r_table_name, c_pk.constraint_name r_pk,
          c_pk_c.column_name
    FROM all_cons_columns a
    JOIN all_constraints c ON a.owner = c.owner
                          AND a.constraint_name = c.constraint_name
    JOIN all_constraints c_pk ON c.r_owner = c_pk.owner
                             AND c.r_constraint_name = c_pk.constraint_name
    JOIN all_cons_columns c_pk_c ON c_pk_c.owner = c_pk.owner
                                AND c_pk_c.constraint_name = c_pk.constraint_name
   WHERE c.constraint_type = 'R'
     AND a.table_name = :TableName
  

• Term plurals changes the name of the foreign key in the relational model

  Hello

  I use a glossary with plurals for entities such as Budget turned to the budgets of the table in the relational model. Unfortunately (for me) it also changes the name of the foreign key. In the related entity, an attribute (for example) is Budget_fiscal year, I expect in the relational model, being the same, but it is transformed into budgets_fiscal_year (budgets in the plural rather than keep him in singular form).

  How can I avoid any change in the attribute names (in the process of engineering in the relational model) but always turn the names of entities from the singular to the plural names for tables?

  Thank you and best regards

  Robert

  Hi Philippe

  Your suggestion 1) works - thank you! budgets_fiscal_year is the attribute of pk exercise in my budget of the entity. It seems a standard behavior of the Data Modeler to compose the UID of the relationship of budgets_fiscal_year (for some reason, this column is not taken the logical model, but the relational model). I would prefer that it be appointed budget_fiscal_year.

  I have not defined any parameter for this (intentionally). But maybe somewhere there by default. Could you tell me where the design parameters in Data Modeler to learn how to configure the definitions mentioned in 2)?

  As I'm always busy with the model of reverse engineering data, I'll wait for DM 4.1.1.888.

  Best regards

  Robert

• Exclude foreign keys from the relational model comparison

  Hello!

  Is it possible to exclude foreign keys for comparison when comparing relational models?

  It's the same and when inporting dictionary of data in the relational model.

  Thank you very much for the help!

  Kind regards

  Dimitar Angelov

  Hi Dimitar,

  Yes it is possible to do using "generate DDL' flag - there is an option in the dialog box"compare models"- tab" Options > compare Options '-C' is a checkbox "use generate DDL settings to filter objects.

  You must make a DDL generation with open physical model that will be used - in the DDL generation options you can deselect items you don't want to have in comparison. You can save as a configuration of generation of DDL or simply do it before the comparison.

  After comparing models of dialog, you can check "Use generate DDL settings to filter objects" box to check (and probably to load a configuration of generation of DDL) and use the buton "refresh trees."

  You can use this method to filter the tables, constraints PK and UK, index, constraints FK and the views.

  Philippe

• Foreign key delete rule: no matching combination does not show a difference to compare models

  Hello

  I've noticed that if there are in the relational model a foreign key with delete rule NO ACTION and in the database (Data Dictionary), the delete rule is RESTRICT, no difference appears in the dialog box to compare. The difference is displayed if the delete rule for example is CASCADE and RESTRICT.

  Kind regards

  Robert

  Hi Robert,.

  Thanks for reporting this problem.  I connected a bug on this subject (21754221).

  This situation does not normally flow when an Oracle database is imported, but may occur when importing other types of database.

  Kind regards

  David

• Show only the keys in the relational model

  I just got 3.1 and I noticed that the new features announced that:
  
  Relational - Option to display only the columns of the primary key, Unique key and foreign key
  
  I looked around and I can't find a way to show just keys only in my relational model (imported data dictionary). It shows the full column list, and it identifies the PK and FK columns in the relational model.
  
  Anyone know where to find this option?

  Right mouse in the area of model

  In the context menu, select 'view details '.

  Then expand and select 'PK, FK, UK columns only.

  It will not resize the objects in the model, so if you want to save space in your diagram, right-click and choose "Resize visible objects."

  Here's a quick look at how it works
  http://www.thatjeffsmith.com/archive/2011/12/SQL-Developer-Data-Modeler-quick-tip-hide-and-resize/

  Note that the screenshot is EA 3.1 so the context menu to "view details" is a little different, but it's the same idea.

• Foreign key constraint, not recognized during the synchronization of data with the model dictionary

  Hello

  Data Modeler is a foreign key constraints do not recognize when synchronizing data with the model dictionary, although the foreign key is there (in the database that a data dictionary is read). I can't find any criterion when a foreign key is not recognized by the Data Modeler. Are there limits to the length of the attribute, or the number of columns in a foreign key, or other limitations which may lead to this behavior not to recognize a fk by Data Modeler? I have columns more than 32 characters. I compared with the fk is recognized by DM, but I can't find anything that indicates why it is not recognized.

  I wonder if someone also has constraints of foreign keys that are not recognized in the comparison of data bases and model?

  Thank you

  Robert

  Hi Robert,.

  Thanks for the comments, I logged a bug.

  Philippe

• SQL Datamodeler: engineer to the relational model: the column names

  Hello
  Suppose I have an attribute called DAY OF BIRTH. Is there a way I can préconcevoir this attribute to a name column DAY_OF_BIRTH?
  
  (I know you might have a column name 'birth day' but is not what I want)
  
  Best regards Erik

  Hi Erik,

  (1) you should check the separation settings in general options > Naming Standard - it should be 'space' for the logic model and "underscore" for the relational model;
  (2) ' apply the translation of the names of "must be selected in the technical dialogue

  Best regards
  Philippe

• PARTITION BY REFERENCE: ORA-02266 when several relatives of foreign key

  Bubble my problem down to a simple example, imagine providers of satellite TV, their programming packages, their clients and customers linking to packages.  Shouldn't be able to drop all data from a provider in one shot?

  CREATE TABLE suppliers

  (provider_name VARCHAR2 (20) NOT NULL)

  CONSTRAINT providers_pk PRIMARY KEY (nom_de_fournisseur)

  )

  PARTITION BY LIST (provider_name) (PARTITION provider__dflt VALUES (DEFAULT))

  /

  CREATE TABLE programming

  (programming_name VARCHAR2 (50) NOT NULL)

  , provider_name VARCHAR2 (20) NOT NULL

  CONSTRAINT programming_pk PRIMARY KEY (programming_name)

  CONSTRAINT programming_fk1 FOREIGN KEY (nom_de_fournisseur)

  REFERENCES (provider_name) providers

  )

  PARTITION BY REFERENCE (programming_fk1)

  /

  Subscribers of CREATE TABLE

  (subscriber_name VARCHAR2 (50) NOT NULL)

  , provider_name VARCHAR2 (20) NOT NULL

  CONSTRAINT subscribers_pk PRIMARY KEY (subscriber_name)

  CONSTRAINT subscribers_fk1 FOREIGN KEY (nom_de_fournisseur)

  REFERENCES (provider_name) providers

  )

  PARTITION BY REFERENCE (subscribers_fk1)

  /

  CREATE TABLE subscriber_programming

  (subscriber_name VARCHAR2 (50) NOT NULL)

  , programming_name VARCHAR2 (20) NOT NULL

  CONSTRAINT Subscriber_programming_pk

  PRIMARY KEY (subscriber_name, programming_name)

  CONSTRAINT subscriber_programming_fk1 FOREIGN KEY (subscriber_name)

  Subscribers of REFERENCES (subscriber_name)

  CONSTRAINT subscriber_programming_fk2 FOREIGN KEY (programming_name)

  Programming REFERENCES (programming_name)

  )

  PARTITION BY REFERENCE (subscriber_programming_fk1)

  /

  ALTER TABLE SPLIT PARTITION provider__dflt values ("dishnetwork") suppliers

  IN (provider_dishnetwork PARTITION, PARTITION provider__dflt)

  UPDATE INDEX

  /

  INSERT INTO suppliers (provider_name)

  VALUES ("dishnetwork")

  /

  INSERT INTO subscribers (subscriber_name, provider_name)

  VALUES ('john doe', "dishnetwork")

  /

  INSERT INTO programming (programming_name, provider_name)

  VALUES ('top200","dishnetwork")

  /

  ALTER TABLE DROP PARTITION provider_dishnetwork UPDATE INDEX providers

  /

  I have same INSERT in subscriber_programming; the above is sufficient to cause the latter to draw "ORA-02266: unique/primary keys in table referenced by foreign keys enabled". ""  Version information:

  -Oracle Database 11 g Enterprise Edition Release 11.2.0.4.0 - 64 bit Production

  -With options for partitioning, Real Application Clusters, Automatic Storage Management, OLAP, Data Mining and Real Application Testing

  -Linux 2.6.32 - 279.11.1.el6.x86_64 #1 SMP Sat Sep 22 07:10:26 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux

  This simple demo is simply representative of course.  Our number of real paintings ~ 60, with hundreds of millions of records in a large number of tables, a tree FK covering several levels of depth, without the partition littered throughout key.  Given that the volume of data, we try hard to avoid executing DELETE, which is why I explore PARTITION migration BY reference.  The problem is not unlike the already-fixed Bug 9329773, but it is slightly different - especially that this variant is not resolved.  If there is no way that such a facility would never fly, you have any suggestions that would not involve changes to application code?  (For example, adding a partition to the tables key column kids won't fly, but I might be able to sell disabling constraints to developers.)

  After much head striking, I found the trick, by https://jonathanlewis.wordpress.com/2006/12/10/drop-parent-partition/ .  The difference of Appendix A is bold: the NOVALIDATE on subscriber_programming_fk2 and the EXCHANGE/CREATE/DROP of programming_e.

  CREATE TABLE suppliers

  (provider_name VARCHAR2 (20) NOT NULL)

  CONSTRAINT providers_pk PRIMARY KEY (nom_de_fournisseur)

  )

  PARTITION BY LIST (provider_name) (PARTITION provider__dflt VALUES (DEFAULT))

  /

  CREATE TABLE programming

  (programming_name VARCHAR2 (50) NOT NULL)

  , provider_name VARCHAR2 (20) NOT NULL

  CONSTRAINT programming_pk PRIMARY KEY (programming_name)

  CONSTRAINT programming_fk1 FOREIGN KEY (nom_de_fournisseur)

  REFERENCES (provider_name) providers

  )

  PARTITION BY REFERENCE (programming_fk1)

  /

  Subscribers of CREATE TABLE

  (subscriber_name VARCHAR2 (50) NOT NULL)

  , provider_name VARCHAR2 (20) NOT NULL

  CONSTRAINT subscribers_pk PRIMARY KEY (subscriber_name)

  CONSTRAINT subscribers_fk1 FOREIGN KEY (nom_de_fournisseur)

  REFERENCES (provider_name) providers

  )

  PARTITION BY REFERENCE (subscribers_fk1)

  /

  CREATE TABLE subscriber_programming

  (subscriber_name VARCHAR2 (50) NOT NULL)

  , programming_name VARCHAR2 (20) NOT NULL

  CONSTRAINT Subscriber_programming_pk

  PRIMARY KEY (subscriber_name, programming_name)

  CONSTRAINT subscriber_programming_fk1 FOREIGN KEY (subscriber_name)

  Subscribers of REFERENCES (subscriber_name)

  CONSTRAINT subscriber_programming_fk2 FOREIGN KEY (programming_name)

  Programming (programming_name) NOVALIDATE REFERENCES

  )

  PARTITION BY REFERENCE (subscriber_programming_fk1)

  /

  ALTER TABLE SPLIT PARTITION provider__dflt values ("dishnetwork") suppliers

  IN (provider_dishnetwork PARTITION, PARTITION provider__dflt)

  UPDATE INDEX

  /

  INSERT INTO suppliers (provider_name)

  VALUES ("dishnetwork")

  /

  INSERT INTO subscribers (subscriber_name, provider_name)

  VALUES ('john doe', "dishnetwork")

  /

  INSERT INTO programming (programming_name, provider_name)

  VALUES ('top200","dishnetwork")

  /

  INSERT INTO subscriber_programming (subscriber_name, programming_name)

  VALUES ('john doe', "top200")

  /

  CREATE TABLE programming_e AS

  SELECT * PROGRAMMING WHERE 0 = 1

  /

  ALTER TABLE programming

  Provider_dishnetwork WITH TABLE programming_e SWAP PARTITION

  /

  DROP TABLE programming_e

  /

  ALTER TABLE DROP PARTITION provider_dishnetwork UPDATE INDEX providers

  /