[Babase] ranker again

Karl O. Pinc kop at meme.com
Fri Oct 6 14:20:27 EDT 2006


On 10/06/2006 11:53:39 AM, Susan Alberts wrote:
> See comments below:
> 
>> 
>> Master-slave (or consistency) relationships among rankings could
>> in general form a directed acyclic graph. In other words, it is  
>> plausible
>> (though it doesn't come up in our case) for one ranking to have two
>> masters (and vice versa). We could invent another "ranking  
>> consistency"
>> table to capture such relationships, but given that we have only a  
>> very
>> small number of ranking types, I'd vote for just a handful of  
>> triggers
>> (probably 4 is enough) to enforce consistency, instead of  
>> complicating
>> the schema further.
> 
> I agree with the points made in this paragraph.

Ok.  I won't make another new table.  But I will add another
column to RNKTYPES, RNKTYPES.Master.  When there's a master
ranktype then the rankings in the given type must be consistent
with the rankings in the master.  I believe this is eaiser
than simply hardcoding the rank type values into the triggers
because if I do that then I have to code in restrictions
as who can change which RNKTYPES when, when
rows can be deleted, etc., so that the triggers
won't do wierd things should RNKTYPES change.  And I'd
have to document all that too.

Is this ok?  If there's any substantive questions
it might be best to have a phone call so we can discuss
things.

Karl <kop at meme.com>
Free Software:  "You don't pay back, you pay forward."
                  -- Robert A. Heinlein



More information about the Babase mailing list