πŸ““ design docs

πŸ˜‡ pub: HXPM Public Issues  |   |  Print Markdown

Here we’ll keep track of some of the design documentation/planning

one of my insane ideas was that β€œi’d like my json files in a directory to be sort of a database queryable via SQL!” and so I implemented the world’s worst sql parser (subsequently replaced with a slightly better one in πŸ““ SQLish ) that would let the user filter flattened json blobs from their β€œβ€β€œβ€β€œdatabaseβ€β€œβ€β€œβ€.

(This is roughly similar to notion’s ability to do the same, except probably worse and less friendly since their’s has nice dropdowns.)


Metadata
Metadata
Key Value
ID PNMR-fSZE/aET
URN urn:penemure:a238ec94-5136-48c5-8567-7d2644fda113
Backend πŸ˜‡ pub: HXPM Public Issues
Ancestors
πŸ“… Created
πŸ“… Updated
Links

Children

Queryable fields

View in API
title<a href="/penemure/note/a238ec94-5136-48c5-8567-7d2644fda113.html"><span class="title">πŸ““ design docs</span></a>
parentsurn:penemure:4d9fe953-c4d9-43d5-ba27-d86bd7d0eefe
version2
created_unix1737490895.662313
updated_unix1739259963.180589
namespaceNone
typenote
ida238ec94-5136-48c5-8567-7d2644fda113
urnurn:penemure:a238ec94-5136-48c5-8567-7d2644fda113
url/penemure/note/a238ec94-5136-48c5-8567-7d2644fda113.html
backendpub
created2025-01-21 20:21:35.662313+00:00
updated2025-02-11 07:46:03.180589+00:00
systemFalse
blurbHere we'll keep track of some of the design documentation/planning one of my insane ideas was that β€œi’d like my json
title_plainπŸ““ design docs
title_txtdesign docs
final_ancestor_titlesPenemure
parent_first_titlePenemure
ancestorsurn:penemure:4d9fe953-c4d9-43d5-ba27-d86bd7d0eefe