> SQL has a knack for doing really easy things well, and moderately complicated things badly. I would assume by default that anything involving graphs should no

> SQL has a knack for doing really easy things well, and moderately complicated things badly. I would assume by default that anything involving graphs should not involve SQL A schema may have only one, or anyway, comparatively very few instances, of recursion. In this case, using two separate data stores would be too much overhead; if the CTE doesn't do anything particularly fancy, that is, if it just retrieves records recursively associated via keys, it's not implicitly hard to debug (actually, there isn't much to debug). A point in case is GitLab's users management, which dropped MySQL also because of the lack of CTEs (at the time).