notesmachine/server/nm-store
Elf M. Sternberg 9337b98ad3 REFACTOR Again! note->note and note->kasten are now separate tables
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.
2020-11-04 17:53:25 -08:00
..
docs Completely revamped the internal structures. 2020-11-04 12:54:17 -08:00
experiments Reverse reference SQL written. 2020-10-29 10:50:31 -07:00
src REFACTOR Again! note->note and note->kasten are now separate tables 2020-11-04 17:53:25 -08:00
.gitignore DOC Phase one committed to the project, the basic layout of the backstore. 2020-09-27 05:35:37 -07:00
Cargo.toml MERGE Shrinkwrap and Comrak updates. 2020-10-13 18:03:12 -07:00
Makefile DOC Rustfmt works. 2020-09-29 08:08:30 -07:00
README.org Note/Page reference relationships now built. 2020-10-16 07:16:57 -07:00

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.

Plans

TODO Make it possible to connect two notes

TODO Make it possible to connect a note to a page

TODO Make it possible to retrieve a collection of notes

TODO Make it possible to retrieve a page