I really doubt that is true.

Is that a template? If not your a great designer!

Are you sure?

Are you sure?

select distinct
‘i$’||tab2.table_name child_tab_name
, col.column_name child_to_parent_ref_column
, child_et.ID child_type_id
, child_et.SHORT_NAME child_type_of
from i$RM_SQL_TABLES tab1
, i$RM_SQL_TABLES tab2
, i$RM_SQL_CONSTRAINTS con1
, i$RM_SQL_CONSTRAINTS con2
, rm_element_types et
, rm_element_types child_et
, i$rm_sql_row_types srt
, i$rm_sql_row_types srt_child
, i$RM_SQL_CONS_COLUMNS col
where et.irid = :master_type_id
and srt.id = et.primary_row_type
and srt_child.id = child_et.primary_row_type
and tab2.irid = srt_child.table_mapped
and con1.table_irid = srt.table_mapped
and tab2.irid=con2.table_irid
and con2.r_constraint_name=con1.constraint_name
and con2.is_owning_fk!=’N’
and col.constraint_irid=con2.irid
and tab2.irid!= con1.table_irid

For example for master element type Entity (:master_type_id = 5002) this query returns:
i$SDD_ATT,ENTITY_REF,5010,ATT
i$SDD_ENTBUN,ENTITY_REF,5012,ENTBUN
i$SDD_RELEND,FROM_ENTITY_REF,5025,RELEND
i$SDD_UID,ENTITY_REF,4877,UID

These steps describe how to create an Application System in Oracle Designer that contains Table and View Definitions for the database objects that make up the Oracle Designer Repository. You will need some PL/SQL packages to get the most refined results; you can download these from the AMIS website

1. Install Designer 9i or 10g Client and Server (Repository, Oracle 9i or 10g SCM)
2. Enable Version Support (in RAU, Menu Options)
3. Create Workarea “Design Capture Designer 10g Meta Model”
3. Get Workarea Irid: Select Workarea, click on Name property,press F5 and copy IRID value to clipboard
4. Create Root Folder Designer 10g Model
5. Get Folder Irid: Select Folder Designer 10g Model, click on Name property,press F5 and copy IRID value to clipboard, paste to some text file
6. Connect to Repository Owner database account using SQL*Plus or TOAD
7. Create the following packages (from the zip-file at http://www.amis.nl): rm_domains, rm_el, rm_col, rm_fk, rm_fk_upd, rm_move
8. Design capture all Domains used by the columns (element properties) in the meta-model:
(examples are: {true,false}, {client,both,server,none}, {char,number,varchar,date,timestamp,….})
- begin
rm_domains.capture_domains
( p_wa_irid => — context workarea Design Capture Designer 10g Meta Model
, p_folder_irid => — target container Designer 10g Model
, p_name_after => ’0′
, p_name_before => ‘G’
);
end;
9. Use the Server Design Capture functionality in the Design Editor to Design capture all Element Types (Primary and Secondary) to Table Definitions:
– first in SQL*Plus or TOAD, connected as Repository Owner, execute this statement:
update SDD_RESERVED_NAMES
set rn_res_name = ‘X’||rn_res_name

this removes the filter on Design Capture that prevents it from Design Capturing Designer’s own elements

– Design Capture (from Design Editor) all i$sdd_… tables
– Design Capture (from Design Editor) all sdd_… views
– Design Capture (from Design Editor) all ci_… views
– update SDD_RESERVED_NAMES
set rn_res_name = substr(rn_res_name,2)

to re-establish the filer

10. Use RM_EL to embellish Element Types/CI-View definitions (note:processing UID fails because setting the alias to UID is not allowed since UID is a reserved word!)
11. Use RM_COLS to embellish column definitions (in view definitions)
12. Use RM_FK to create foreign keys for view definitions
13. Use rm_fk_upd to define ARCs for the foreign keys