The TreeView loads all children recursivly. It is not possible to implement load-on-demand as it is possible for the TableView. It is also a memory problem if all children are loaded - and if you have many elements!
Example: Database table with millions of records, self joined
We create a tree with the hierarchically representation of the records. We have a custom model which reads a resultset but only needed rows, not all because it is possible that the statement is not very fast.
If the tree loads all children recursivly, then we get an out of memory exception or the tree is very slow....
It would be better to load children when expanding an item and best if not all children are loaded at once (should work like the TableView)
Maybe there is a solution for above use case?
Example: Database table with millions of records, self joined
We create a tree with the hierarchically representation of the records. We have a custom model which reads a resultset but only needed rows, not all because it is possible that the statement is not very fast.
If the tree loads all children recursivly, then we get an out of memory exception or the tree is very slow....
It would be better to load children when expanding an item and best if not all children are loaded at once (should work like the TableView)
Maybe there is a solution for above use case?