Package release: Org-Roam-UI

Given what is saved in the DB (title, position, olp) we can actually derive hierarchical links from the DB, see WIP: Infer the implied links represented in the org-mode hierarchy. by blester125 · Pull Request #53 · org-roam/org-

The problem is that this involves multiple self joins on the node table, which I would think will get rather large for most users and could result in slow downs. Adding more indexes to the DB could help, but it looks like the LIKE query to find nodes from the olp would never use the INDEX (the right hand side is not a string literal The SQLite Query Optimizer Overview). It is also a complex query that could be hard to maintain. Plus, UIs like org-roam-ui where the whole graph is sent each time need to either pay this cost each time or get a lot more complex by supporting graph updates via diffs.

If org-roam managed saving these links (with a different link type?) in the DB it would make any graphing effort a lot easier, even if org-roam just ignored them. It seems like org-roam, which has access to the actual file would make storing these hierarchy links a lot easier. I guess the trade off is should org-roam store/create this data that it will probably never need/use or should it be derived by those actually using at the cost of having to make sure it is optimized.