Oracle Designer 6i repository tables relationships

[ITDave]

We currently run Oracle Designer 6, and have many bits of SQL & PL/Sql that produce useful reports direct from the repository (such as tables with duplicate sequence numbers; list arcs in an application; list constraint names; foreign keys with no columns defined etc. etc.). The main repository tables we used were ci_table_definitions, ci_application_systems, ci_constraints, ci_key_components, ci_columns, ci_diagrams, ci_diagram_element_usages , cdi_text, ci_entities & ci_attributes. We had a good understanding of how these tables related to each other.

Does anyone know how the Designer 6i repository is laid out? I see that there's still ci_table_definitions, ci_columns and some other familiar views, but in which tables are the information about containers & workareas & configurations & various versions ? - and how do these relate to ci_table_definitions (and the others mentioned above) ?

 

[JFlack]

One of the things I hated most about the transition to Designer 6i is the way they broke all of my API reports and utilities. The API hasn't really changed much, but what has changed has a far reaching effect - the primary keys. For most purposes, the new PK is the new column, IRID. If you replace all your references to ID with IRID, you'll be 90% of the way to getting your API stuff to work again. For the other 10%, you should check the new docs - changes vary according to what you want to do, particularly if your program updates the repository.

 

[timofe]

The key piece of information for my reports was that ci_application_systems joins to other views (e.g. ci_table_definitions) via ci_folder_members.

For example:

WHERE ci_folder_members.member_object = ci_table_definitions.id
AND ci_folder_members.folder_reference = ci_application_systems.id

joins application systems to table definitions.

If anyone finds/writes any code converters: please let me know!

Cheers,

Tim