Work in progress, release notes for 3.1 #3963
Conversation
|
|
||
| .. _fix-mptt: | ||
|
|
||
| ``fix-mptt`` |
There was a problem hiding this comment.
Is this command going to remain in 3.1? I thought I had heard it wouldn't.
There was a problem hiding this comment.
Possibly not, but since we tell people to use it in the release docs, it had better be explained!
There was a problem hiding this comment.
Perhaps a pointer to the previous version's docs then? I can't make sense to document a command that isn't present.
There was a problem hiding this comment.
I can't see a way around it - there weren't any docs previously, which is why I added this.
There was a problem hiding this comment.
fix-mptt is replaced by tree in 3.1 (I totally overlooked this change!) which has the same role
|
|
||
| Over the years MPTT has proved not to be fast enough for big tree operations (>1000 pages); tree | ||
| corruption, because of transactional errors, has also been a problem. | ||
|
|
There was a problem hiding this comment.
It is my understanding that MPTT (Modified Preorder Tree Traversal) is a general logical topic and that both django-mptt and django-treebeard implement concrete solutions around this. This above reads like MPTT is a product that we have abandoned in favour of Materialized Path. I don't think this is correct. I think we should replace "MPTT" with "django-mptt" in the above paragraph, and in the one below.
There was a problem hiding this comment.
@mkoistinen MPTT is a specific algorithm, different from the one implemented by treebeard, so I think current wording is ok: we're not replacing an MPTT implementation with another, but one tree-to-relational algorithm with another
|
As agreed with @evildmp I'm merging this as preliminary 3.1 release notes. More work will follow before final release |
Work in progress, release notes for 3.1
Do not merge!