Re: Nearest Common Ancestor Report (XDb1's $1000 Challenge)

> I saw that you wanted a GENERIC solution, that would allow
> ANY hierarchy. That's why I renamed the table "hierarchies", added the
> hierarchy column and added a parameter to the procedure.

Actually the provided solution is inconsistent in that the class hierarchy of things, the most important one, isn't encoded in the hierarchies table. It is instead encoded in a dedicated table named types. The procedure that generates the report utilize hierarchies table and not the types table. And if one were to encoded the class hierarchy in hierarches table also, it would be redundant and possibly different. Received on Sun May 23 2004 - 02:54:14 CEST