-
Notifications
You must be signed in to change notification settings - Fork 23
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
Think about a replacement for mptt (no longer maintained) #71
Comments
Unfortunately it's not maintained anymore. |
There are a few more packages that do the same thing as mppt.
And some Postgres only packages |
Maybe start with - https://github.com/jokiefer/django-mptt2/ that @jokiefer maintains. |
I looked at the various tree-packages for django last year. This was not related to this issue but for another application. I found django-tree-queries most interesting (as @vittoriozamboni). It is from one of the ex-maintainers of django-mptt. He wrote an interesting blog about about his motivation. But switching to django-mptt2 is probably the easiest step forward (I have not tried). |
keep in mind, that djang-tree-queries has some disadvantages about django prefetching technics, cause it uses raw queries. That's one reason why i need to start my own project with django-mptt2. An other reason was, that django-treebeard, which also implements a nested set, is that there are no thread safeativity. If there is a package which solve boths, my mptt2 package is not needed. My mptt2 package is also only supported for django >= 4.2. EDIT: another hint: # example index extension
indexes = [Index(fields=("tree_id", "lft", "rght"))] So if someone uses this indexes, he can't migrate to django 4.1. But this is only my opinion, which i want to tell about. I never used |
I am conscious that relying on an unmaintained library is both a risk and a pain, but unfortunately I don't have the capacity at the moment to evaluate new core libraries and test them for a successful migration. If I release a new major version (i.e. 2.0) with a new dependency the package might still be installed for loosy requirements settings ( Ideally, the new core library should be installed and migrated, without losing tree information already stored in DB. I would avoid platform specific libraries like I am more than happy to accept pull requests with successful migrations included, and with all tests passing. To test new releases, I relied on django-groups-manager-migrator small project, where I am loading data, changing version, and run a small suit again. |
mppt used to model group hierarchies is no longer maintained. This is probably not a big problem for a while.
Switching to another tree library could be done as part of a 2.0 release.
The text was updated successfully, but these errors were encountered: