Data types
A data type is the form a value takes in the database. Each of the 14 property types stores its value as one data type.
Example: “Morning run” has Distance 5.2 (a number), Type Run (a list of tags), Done true
(yes/no) and Project [[Projects/Spring race]] (a link).
The data types
| Data type | What it holds | Example |
|---|---|---|
| Text | characters | Ursula K. Le Guin |
| Number | one number | 5.2 |
| Date and time | a moment in UTC (world time), with a time zone where the wall-clock time matters, or a plain date for all-day values | 2026-10-27 07:00, Europe/Vilnius |
| Yes/no | true or false | true |
| List | several members, one row each | the tags Run and Morning |
| Link | a pointer to another entry, by its id | Project: Launch |
| File | a record of a file: name, size, checksum, which entry uses it | pancakes.jpg |
| JSON | structured data with named fields and lists | a GPS route |
A Block page and a Dashboard hold blocks. A Block page merges word by word; a Dashboard merges tile by tile. Both use Loro, a library for text and documents that many devices edit at once.
Each property type
| Property type | Data type |
|---|---|
| Text | Text |
| Block page | blocks from top to bottom (Loro); plain markdown in the folder |
| Dashboard | tiles, each one block with a place and a size (Loro) |
| Number | Number |
| Checkbox | Yes/no |
| Date | Date and time |
| Tags | List of tag ids |
| Relation | List of links |
| Children | nothing stored; each child stores its Parent link |
| Media | List of files |
| JSON | JSON |
| Stopwatch | not decided yet |
| Scaler | not decided yet |
| Formula | nothing stored; computed each time |
How the database keeps values
- One value table. Each value is one row: the entry, the property and the value, in a real column for its data type. Views filter and sort fast because each column has an index.
- Lists are one row per member. An entry with two tags has two rows. So two devices that add different tags offline keep both.
- Ids, not names. Tags, links and formulas point by id, so a rename never breaks anything. Ids are made on your device (UUIDv7, a long id that sorts by time).
- Time in UTC milliseconds everywhere. The time zone is kept only where wall-clock time matters: the Entry date, Date values and schedules.
- Later edit wins for a single value when two devices change it. A Block page merges word by word, and a Dashboard merges tile by tile.
- Files stay files. The database keeps the record; the bytes live once in
Attachments/.