I'm trying to understand the code for acs_attributes.
attribute::add creates an additional column in the table for that object_type based on table_name in acs_object_types.
Why? Is there supposed to be a trigger ceated somewhere that populates this column automatically?
This does not seem to match the way dotLRN uses attributes
dotlrn_community::set_attribute inserts a value in acs_attribute_values.
Why is this a dotLRN proc? Is there a core proc that sets attribute values?
To retrive attribute values dotLRN seems to cache a list of attribute values for each community and access it through a tcl API rather then views.
Based on the dotLRN code it seems like adding a column when you add an attribute is wrong, but perhaps it is necessary for CMS?
