Query PowerDesigner for the current Model

[freym05]

I am looking to query the PowerDesigner Repository to return the current / latest Model version as is displayed in the Object Browser Repository Tab. The PMOBJT LVRS column is flagged for many versions and doesn't seem appropriate for this use. Any suggestions or thoughts?

[freym05]

Just to render a close to this, for everyone's information PowerDesigner builds the Object Browser Repository Tab Tree map of Models and their current versions from PMOLOG table looking for the latest version via NAME and VRSN columns. It is then possible to traverse all child objects via the PMOBJT Objects.

The PMOBJT LVRS seems to have a different purpose other than the austere description within the installation materials "Repository Metamodel" PDM.

[GeorgeMcGeachie]

Thanks for the info, Micahel 🙂

[freym05]

George, to clarify the latest version of the Model Object is in PMOBJT, correct? When you say Current Branch, we have some Models that haven't gone through any "branching" per se. The issue is that multiple PMOBJT Model objects have the LVRS set to 1, and every branch doe as well, not just the current branch. I could certainly be missing something. Thx.

[GeorgeMcGeachie]

Sorry, I'm not going to guess where and when PD does things in database tables and columns. I stick to the API and object model.

[GeorgeMcGeachie]

I don't know why you're looking for the name of a column to access metadata about an object in the PD interface - in the object model, the version for the latest version of a repository model object in the current Branch is held in the Version property.

[freym05]

Unsure of your need to know, however I need the capability to report on current Model content to provide concise socialized metadata (including custom tacit metadata) regarding our orgs data assets. Think of it as how do we optimize the investment of the new currency (i.e. data) within the enterprise? I suspect this is a higher level that you originally responded to? Thanks for the effort.

[GeorgeMcGeachie]

Thanks for the clarification, Michael. I was merely wondering aloud why you were accessing the database directly (presumably with SQL), rather than accessing it via the API, hence my comments about the object model. I expect you're using the tools that work for you. Personally, I'd rather use a scripting language, mostly because I've never written SQL - I know that's heretical in some data modelling circles, but there you go.