Task #13237

Reconsider nested set implementation in some models

Added by José Raddaoui Marín about 1 month ago.

Status:NewStart date:01/13/2020
Priority:MediumDue date:
Assignee:-% Done:

0%

Category:Data model / ORM
Target version:-
Google Code Legacy ID: Tested version:
Sponsored:No Requires documentation:

Description

The following models use nested set:

- Actor
- Repository (inherited)
- Function
- InformationObject
- Menu
- PhysicalObject
- Taxonomy
- Term
- AclGroup

We should investigate in which models the nested set is actually needed and remove it if it's not. Without being a major performance improvement, it could speed up the deletion of those models and simplify the AtoM code.


Related issues

Related to Access to Memory (AtoM) - Task #13224: Improve hierarchy management queries Code Review 12/09/2019

History

#1 Updated by José Raddaoui Marín about 1 month ago

  • Related to Task #13224: Improve hierarchy management queries added

Also available in: Atom PDF