Aspect Backend Implementation

udeleng

I have some questions on how aspect attributes are implemented by the content server:

1. Qualifiable properties exists as columns in the 'r_' or 's_' table for the object to which they are attached, where as, non-qualifiable properties are stored in the i_property_bag and r_property_bar attributes, correct?

2. In Composer, if I check the 'Non-Qualifiable' option for an attribute, is that same same as the OPTIMIZEFETCH option?


3. For qualifiable properties, when are the aspect specific columns created? Are they created when the aspect is attached or are they created when the aspect is installed?

4. If they are created at install time, this would mean that selecting 'Target Object Type' in the aspect module's 'Aspect Type' tab in Composer is mandatory, correct?

5. If the aspect uses qualifiable properties, to uninstall the aspect I will delete the aspect folder under /System/Modules/Aspect (just like for a TBO or SBO), and then delete the columns in the attached type's tables?

I wanted to know this in advance to avoid possible irreversible mistakes.

udeleng

I found some answers to my questions:

Each  aspect gets a table in the RDBMS with columns matching the aspect  attributes, and some additional columns to relate the aspect to a  specific object. I created one attribute as qualified attribute. So in the case of Oracle, the table had the following  name:

     DMI_03038B838000020B_S:

          R_OBJECT_ID - VARCHAR2(16)

           I_PARTITION - NUMBER(10,0)

          MY_ATTR1 -  VARCHAR2(128)

When an aspect is attached to an object  (I didn't specify the aspect for specifc types), an entry is created in  the above table. An entry is created in the same table for each object  to which the aspect is attached. If the aspect is detached, the entry  for that object is deleted from the said table.