Appearance
Database views
A database view is a saved query over pages, shown as a table or a board.
Type /database to insert one. The editor beside it sets what it selects, which columns it shows, how it sorts, and how it is laid out.
Rows are pages
This is the design in one sentence, and everything else follows from it.
- A row is a page.
- A cell is one of that page's properties — or one of three page fields addressable as if they were properties:
title,slug,journalDate. - The first column is the link to the page itself.
The table holds nothing. Deleting a view loses nothing, because there was never anything in it — the data is on the pages, where you can edit it in the ordinary way, and where it stays readable if you stop using Notesflow.
Why there is no id column
A view cannot ask for a page's identifier. A UUID must never appear in exported text, and a column of them is precisely the Notion-export failure this design exists to avoid.
What a view selects
| Setting | Meaning |
|---|---|
| Under | Rows are the descendants of one page, or the whole workspace. |
| Match | Whether a row must satisfy all the conditions or any of them. |
| Where | The conditions themselves. |
| Columns | Property names, in display order. |
| Sort | One or more keys, each ascending or descending. |
| Limit | How many rows to show. Absent means all of them. |
A subtree is how a "database page" is expressed without inventing a container type. The rows are just its child pages, and they remain ordinary pages — openable, editable, exportable, linkable.
The comparisons
Deliberately few, and all of them total — every one gives an answer for every value, including a missing one:
eq, ne, gt, gte, lt, lte, contains, exists, empty.
Table and board
A layout is a view concern and nothing else: the same query, the same rows, the same pages.
A board groups by a property, and each distinct value becomes a column. Drag a card from one column to another and it writes that property on the card's own page — which is the only thing it could honestly mean, since the card is a page and the column is a value.
Rows whose group value is missing or empty get their own heading rather than being dropped. A card with no status is exactly the card somebody needs to find.
What a view exports
A view is T3, and the degradation is worth understanding because it is the good half of a trade:
- It exports as a real GFM table of the rows the query selected, with the first column linking to each row's own
.mdfile. The rows are ordinary exported pages, and their cells are those pages' frontmatter — so nothing is trapped in the table. - The query itself — the filters, columns, sort and layout — lives in a small
.base.yamlfile beside the export.
A reader who ignores the sidecar sees a table frozen at the moment of export rather than a live view. What they do not get is a wall of identifiers, or a CSV whose rows exist nowhere else.