Change of Stereotype Name Results in New + Old Nam

[wikitect]

In my custom MDG for TRAK I'm trying to change the names of certain
stereotypes and relationships to make them read more like normal english
e.g. 'EnterpriseGoal' becomes 'Enterprise Goal' and 'hasPart' becomes 'has part' etc

Once released this then leaves existing users with their existing old stereotype names plus anything newly created will take the new names. In order to help I therefore want to provide an easy means for others to update their entire project at one go hence thought SQL should do the job nicely.

For an object:

Code: [Select]

UPDATE t_object
SET Stereotype='Architecture Description'
WHERE t_object.Stereotype='ArchitectureDescription';
For a connector:

Code: [Select]

UPDATE t_connector
SET Stereotype='hosted on'
WHERE t_connector.Stereotype='hostedOn';
the problem is that the changed object/connector then has both the old
and new stereotypes e.g. Architecture Description, Architecture
Description

Is there another table of column that needs to be modified and where it
is picking up the old value or do I need to do something else?

The Sparxians advise that use of SQL is not supported and that I should use a script (which apart from being much slower takes much more time to get into and develop).

Anyone any constructive suggestions on what I may have missed or where the existing (old) stereotype names might be coming from?

[Geert Bellekens]

Yeah, look in t_xref.

Geert

[wikitect]

Thanks, Geert