Closed fabiocaccamo closed 3 years ago
What about today?
The status didn’t really improve. I use django-tree in one project, but I don’t have enough time to work on this. Also, I quite lack the motivation now. I’ve been working on a ton of other projects since, and I never faced a situation yet where using django-treebeard was really more annoying than it would be annoying to port django-tree to MySQL & SQLite.
So for now it’s the status quo. I will keep updating django-tree for the project I created that uses it. But it will likely never have stable release & documentation. I know that’s a waste, given all the time I spent on it and the quality of the test suite I created. But it’s not a rational argument in favour of putting a lot of effort into this.
If some high-skilled SQL developer has the motivation to finish this, I’m totally open to gradually handing her/him over the project :)
@victorct-pulsarup some time ago I was in your same situation till I decided to write django-treenode
.
Is it worth documenting the work needed to port to MySQL or even Sqlite somewhere ?
You never know, someone might pick it up (may even be worth seeking funding for same).
@stuaxo I’m not sure there’s a lot to describe. To have MySQL or SQLite support, ideally an SQL trigger has to be implemented to batch update the paths in the same transaction, or worst case scenario put the logic in a Django signal.
This question can be split in three parts:
Here are the answers: