Elf M. Sternberg
9337b98ad3
This was getting semantically confusing, so I decided to short circuit the whole mess by separating the two. The results are promising. It does mean that deleting a note means traversing two tables to clean out all the cruft, which is *sigh*, but it also means that the tree is stored in one table and the graph in another, giving us a much better separation of concerns down at the SQL layer. |
||
---|---|---|
.. | ||
docs | ||
experiments | ||
src | ||
.gitignore | ||
Cargo.toml | ||
Makefile | ||
README.org |
README.org
Notesmachine Store
This is the storage layer for Notesmachine. It supports the retrieval of the basic information from Notesmachine, but it never reveals the underlying mechanisms by which it performs its magic. The "ids" leaving this API will always be the textual ids used in all public representations:
- Boxes are referenced by slugs, and clients must accept uniqueness failures.
- Notes are referenced by "friendly_id" format strings, which are base-62 formatted versions of UUID4 strings.