3 ms·
Reading the entire structure into memory brings all kinds of problems with it, such as knowing when to throw out your in-memory copy because the database change
by derobert 17y ago
Reading the entire structure into memory brings all kinds of problems with it, such as knowing when to throw out your in-memory copy because the database changed. It is also problematic if the tree is large.
Reading the entire tree into memory can be effective if it never changes and is reasonably sized. But if that's the case, why are you storing it in a database? Why not just a data file?
- rjurney 17y agoIn practice... in many applications you can cache parts of the tree in a session, because it won't change in a single login. If its not too big.