Forum OpenACS Development: acs_named_objects obsolete in openacs 5.2+ ?

Request notifications

can someone confirm or disprove my assumption that acs_named_objects is obsolete? in essence, the table acs_named_objects adds an object_name and package_id to an object_id. Since OpenACS 5.2, we have this information in acs_objects.

However, the categories documentation (e.g. http://openacs.com/test-doc/tutorial-categories) suggests to update acs_named_objects.

Furthermore the datamodel for postgres and oracle is different (see below). Especially, the added attribute 'locale' will probably cause problems due to the FK, when acs_named_objects is used as documented (see below). The only application in the cvs repository aside from xowiki using categories "by the book" with acs_named_objects is faq.

So, is there any reason to keep the table acs_named_objects?
-gustaf

Postgres:

create table acs_named_objects (
object_id integer not null
constraint acs_named_objs_pk primary key
constraint acs_named_objs_object_id_fk
references acs_objects(object_id) on delete cascade,
object_name varchar(200),
package_id integer
constraint acs_named_objs_package_id_fk
references apm_packages(package_id) on delete cascade
);

Oracle:

create table acs_named_objects (
object_id integer not null
constraint acs_named_objs_object_id_fk
references acs_objects(object_id) on delete cascade,
locale varchar2(5)
constraint acs_named_objs_locale_fk
references ad_locales,
object_name varchar2(200),
creation_date date default sysdate not null,
package_id integer
constraint acs_named_objs_package_id_fk
references apm_packages(package_id) on delete cascade,
constraint acs_named_objs_pk
primary key (object_id, locale)
);

Collapse
Posted by Dave Bauer on
It looks like it contains additional information such as locale, which we don't support per object, but otherwise seems to duplicate acs_objects. This was added prior to title and package_id being added to acs_objects, and I agree it should be removed.