Akash akashpal-21

Introduction

While using Org-roam - the data is stored across tables in the database. The tables are as follows

(files . file title hash atime mtime)

(nodes . id file level pos todo priority scheduled deadline title properties olp)

	;; README — org-roam-sequence
	;;
	;; Helpers
	;; -------
	;; org-roam-sequence-id-split (id)
	;; > split "1a2" -> (1 "a" 2).
	;;
	;; org-roam-sequence-id-join (parts)
	;; > join (1 "a" 2) -> "1a2".
	;;

	;; org-roam-link-utils.el -*- Some utilities for managing org-roam links ("roam:")


	;; HHHH---------------------------------------------------
	;; Customisations

	;; Do not auto transform "roam:" links to "id:" links on save.
	(setq org-roam-link-auto-replace nil)

	(defun org-roam-link-replace-all--export (backend)

	;; org-roam-node-read+.el

	(require 'org-roam-node)

	;; Add a new constructor function to the org-roam-node struct
	;; This constructor function avoids using &keys, and only takes a
	;; curated lists of slots to construe the node struct.
	(cl-defstruct (org-roam-node (:constructor org-roam-node-create)
	(:constructor +org-roam-node-create
	(id &optional file-title file-mtime level point file title olp))

	;; org-roam-node-cache.el

	;; When `org-roam-node-read' is called --
	;; `org-roam-node-read--completions' is initiated which fetches the list of struct nodes, applies FILTER-FN if any,
	;; then formats them as specified by `org-roam-node-display-template' and finally
	;; after sorting according to `org-roam-node-default-sort' or user SORT-FN
	;; passes this final list further down.

	;; `org-roam-node-read--completions' makes two subcalls -
	;; A. To `org-roam-node-list' which queries the db and generates a nodes struct for each node.