Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Evaluate the best option for hierarchical modeling #46

Open
1 of 2 tasks
eronlloyd opened this issue Nov 26, 2022 · 1 comment
Open
1 of 2 tasks

Evaluate the best option for hierarchical modeling #46

eronlloyd opened this issue Nov 26, 2022 · 1 comment
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@eronlloyd
Copy link
Member

eronlloyd commented Nov 26, 2022

Description

MPTT or CTE? I'm not yet sure this is going to be an issue, but better to design it properly up front. Based on my previous notes, this might be the solution.

Requirements

  • Efficiently represent hierarchies in the database

Dependencies

  • django-tree-queries

Tasks

  • Write code
  • Write documentation
@eronlloyd eronlloyd added the enhancement New feature or request label Nov 26, 2022
@eronlloyd eronlloyd added this to the Release 0.1 milestone Nov 26, 2022
@eronlloyd eronlloyd self-assigned this Nov 26, 2022
@eronlloyd eronlloyd changed the title Evaluation best option for hierarchical modeling Evaluate the best option for hierarchical modeling Nov 26, 2022
@eronlloyd
Copy link
Member Author

I decided to go with django-tree-queries, and the implementation went smooth. The parent field was simply replaced by the one provided by the core.CRMTreeBase abstract model, which will be used for any model needed hierarchies of itself.

@eronlloyd eronlloyd reopened this Oct 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant