Elf M. Sternberg
da44610098
This is pretty hairy, because we're relying on the LEFT JOIN feature
to give us the root node when we need it. That's kinda ugly, but
it seems to work just fine. It also gives us the list in the
*correct* order, so the only thing we need to do is go to the last
item in the returned vector, make sure it's a root node, then go
fetch the page so we can decorate the list with the *right* root.
We'll pass this as a JSON object { [notes-in-reverse], page }.
|
||
|---|---|---|
| .. | ||
| 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.