Analyze full removal of nested set in favor of the current parent relation plus an order column
|Category:||Data model / ORM|
|Google Code Legacy ID:||Tested version:|
MySQL 8.0 will be a requirement for AtoM 2.6, due to the inclusion of CTE in the ancestors queries (see #13220 and #13224). This brings up the possibility to also use CTE in the descendants queries and remove the need of a nested set implementation on the hierarchical models.
With the enhancements and tests made on #13224, using CTE to fetch descendants won't be an improvement in most of the cases. However, it will allow us to remove the
rgt columns entirely, which will improve (a lot on big data-sets) the insert, move and delete operations of those resources.
In general, we should analyze if we prefer a better performance fetching the hierarchies or making changes to them.