Org as a db?
Table of Contents
In everyday life
Versioning these blog posts with org-roam and not git
I insert one org-roam noade for every new blog-post I –rarely write and often update– here and quite often I want to know how did I end up with the current version of the post.
Find that node with org-roam to edit it, instead of default drafts
edit, save , exit , now I have both versions in my-graph.
To publish I ll just ./bb.sh edit $PostName , find the node1 and expost the latest PostNamedotorg as html and replace that with html of existing post , save, exit scp.
risks of evolution
you can use properties drawer to implement simple database capabilities, but it has one important limitation - values are mere text, so you can’t have real Org mode links there, meaning that Element API, Org roam and some other tools do not recognise them as links.
agenda on top of the cached data? , to instead expose an API to build the interface from a different data source
will org-roam’s caching model work at larger scales? rgrep isn’t magic, it’s literally just grep -r or recursive grep, something that all *NIX users are familiar with
org-roam’s functions are just a read-only interface on top of the database layer. how can users specify their own schema, when the schema and how the database is populated is very much tied to what’s being pulled out of each Org file?
should org-roam provide a core for managing metadata (including links) with APIs to build on top of that (like org-roam-buffer, dailies, agenda and other stuff) which could be shared either in the org-roam repository or separately.
Footnotes:
Unlike node name, the name of the file will change after every edit, but thats no trouble , as org-roam searches by node name and not by file name
Created: 2022-11-16 Wed 10:26