October 18, 2011
Recently I had the need to use a pseudo relation as part of a path evaluation (i.e. as part of a business rule path). But, the path evaluator can’t do this, because it’s not a “real” relation in the Clarify/Dovetail schema. Pseudo Relations I covered pseudo relations in my recent Schema 201 webinar, but lets give a quick review. A pseudo relation is a sort of schema hack that implements a relation using two fields. One field holds the type_id of the object that we want to relate to, and one field holds the objid of the object. These pseudo relations were a bit of a data modeling hack, before exclusive relations. Pseudo relations are nice, because we don’t have to create a new physical column for a relation, and we can relate to any other object in…
Transform a Pseudo Relation into an Exclusive Relation
October 18, 2011
Recently I had the need to use a pseudo relation as part of a path evaluation (i.e. as part of a business rule path). But, the path evaluator can’t do this, because it’s not a “real” relation in the Clarify/Dovetail schema. Pseudo Relations I covered pseudo relations in my recent Schema 201 webinar, but lets give a quick review. A pseudo relation is a sort of schema hack that implements a relation using two fields. One field holds the type_id of the object that we want to relate to, and one field holds the objid of the object. These pseudo relations were a bit of a data modeling hack, before exclusive relations. Pseudo relations are nice, because we don’t have to create a new physical column for a relation, and we can relate to any other object in…