/build/static/layout/Breadcrumb_cap_w.png

Trying to understand the relationship of the ASSET tables?

When viewing the system DB I find multiple ASSET tables and have yet been able to determine the key relationships between ASSET/ASSET_ASSOCIATION/the many ASSET_DATA_X and so on. What are the 'key' fields required or to use when building queries that will tie them together? Should I be concerned with ASSET_HIERARCHY or ASSET_FIELD_DEFINITION????

0 Comments   [ + ] Show comments

Answers (1)

Answer Summary:
Posted by: Roonerspism 12 years ago
Second Degree Brown Belt
1
It depends on the sorts of queries that you're trying to write. I have not bothered with heirarchy at all, you wouldnt unless you were using nested assets. Field definition however can help you find out what sorts of fields are where and allow you to search by text name of the field as opposed to the field type/id. Its a little messy but once you get your head around it reading it is okay.
Looking at the asset_field_definition table and its contents will help you figure out which tables relate to eachother etc.

Comments:
  • If you like throw me an email for some extra info. - Roonerspism 12 years ago

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ