ProposalAdd object_name to acs_objects table. See here
ReasonMost of the objects are in some way displayable and named (except for some internal objects such as acs_rels). Services such as categories or search need to be able to display (potential) long lists of objects with their names and let the user sort by the name. Doing this by using the current acs_object.name interface in pl/sql is inefficient and unscalable for longer object-lists and does not solve the problem to order by that name.
DisadvantagesSome objects don't have a name and therefor will need to store null values. We will need to duplicate inserts and updates on the pretty names of the package-specific tables. We will only store the names in one locale, so multilinguality is not supported.
SolutionAdd triggers or change pl/sql functions for every package with named objects. Add and change core functions. Add column "object_name" of type varchar2(200) (or something the like) to table acs_objects without a "not null" restriction.
Will do the changes of the core and the packages news, forums, blogger, file-storage, categories, mailing-list and someone else should change the other packages.