Book a Demo

Author Topic: EA Project Model for the Database Oracle  (Read 3827 times)

Mario Rodriguez Jaen

  • EA Novice
  • *
  • Posts: 6
  • Karma: +0/-0
    • View Profile
EA Project Model for the Database Oracle
« on: July 08, 2011, 08:55:18 pm »
hi,

I´m trying to find documentation on how the database tables for Oracle are mapped to the EA object model. For example, I have look at the scripts for creating the Oracle database and I´m unable to find the equivalent table for the Package object.

I have read several postings and it seems the the t_object table is the place to look.

My need arises because I have to automize a reporting feature that is based on a structure for EA projects and wanted to use the database for reading such info. The EA projects are BBDD based

Any help to this newcomer is welcomed.
 :)

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: EA Project Model for the Database Oracle
« Reply #1 on: July 08, 2011, 10:03:29 pm »
Mario,

Often the related table is mentioned in the documentation of the API

The rest you'll have to work out by trial and error.

Geert

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: EA Project Model for the Database Oracle
« Reply #2 on: July 08, 2011, 10:05:46 pm »
By the way, package is a special case. Some of its properties are stored in the package.element object.
So for each package you will find a record in both t_package as t_object.
The are related by package_id in the pdata1 field.

Geert

Mario Rodriguez Jaen

  • EA Novice
  • *
  • Posts: 6
  • Karma: +0/-0
    • View Profile
Re: EA Project Model for the Database Oracle
« Reply #3 on: July 08, 2011, 10:08:31 pm »
thanks Geert

Yes, it is pretty much self explanatory. The object type is where the definition is saved; for example, package, requirement, use case.

And then there is a grouping of elements by package_id.

I think that is all what I need.