Tag: customization

Here's an interesting scenario that we recently ran into when developing our SchemaEditor application for Clarify. In Clarify, the rule is that relation names must be unique within a table, which makes sense. For example, I cannot have two relations named case2site on the case table. The schema editing tools (ddcomp, DD Editor, Dovetail SchemaEditor) will disallow this. But there is no problem having case2site on the case table and case2site on the subcase table (although it's a bad naming convention, it's not illegal). However, in Microsoft SQL Server databases, Clarify creates relate stored procedures for relations. For example, the following relation: case2subcase OTM subcaseINV_REL=subcase2case COMMENT="Subcases originated from the case" will produce the following stored proc: create procedure rl_case2subcase( @case1 int, @subcase2 int) as update table_subcase set subcase2case = @case1 where objid=@subcase2 How and where do these stored procs get used?…