On Fri, Dec 1, 2017 at 8:32 AM, Julien Grillot
wrote:
> At the moment, both SELECT LCA('1.2', '1.2'); and SELECT LCA('1.2',
> '1.2.3'); return ‘1’.
>
> According to the Wikipedia1 definition of LCA:
> “[…] the lowest common ancestor (LCA) of two nodes v and w […] is the
> lowest (i.e. deepest) node that has both v and w as descendants, where we
> define each node to be a descendant of itself (so if v has a direct
> connection from w, w is the lowest common ancestor).”
>
> So, in my understanding, both SELECT LCA('1.2', '1.2'); and SELECT
> LCA('1.2', '1.2.3'); should return ‘1.2’. What do you think about it?
>
If indeed one defines "each node to be a descendant of itself" then you
are correct. Unfortunately your example indicates that this implementation
does not define ancestry that way. While you may not agree with the
definition at this point changing the existing function's behavior in this
manner seems highly undesirable - too much existing code would silently
break. Adding a leading (due to varargs) boolean argument that specifies
"end node is ancestor of itself" behavior might be a workable solution.
Regardless, the docs should be clarified on this point, though, and maybe
add a code comment somewhere.
David J.
