Skip to content

Wiki databases

Your own space is Solo plan.

A space can hold structured data in addition to prose: a table with typed columns, appropriate where a list has outgrown a bulleted format.

A database in a wiki space — typed columns, rows, and the view barOpen /s/me in the app
A database in a wiki space — typed columns, rows, and the view barA database in a wiki space — typed columns, rows, and the view bar

Databases open as a panel over the space rather than as a separate page. The database icon in the page toolbar opens the panel, and the back arrow returns to the list.

Fifteen column types are available. The final four distinguish a database from a spreadsheet:

Basic text, long text, number, date, checkbox, URL, email
Choice select, multi-select, status
People person
Linked relation, rollup, lookup, formula

A relation links a row to rows in another database. A lookup retrieves a value across that link, a rollup aggregates the linked rows, and a formula computes from the row itself. Together they allow a database to remain accurate without duplicating values.

Rows can also open as pages, so a record can carry its own written page rather than being confined to a cell.

Rows can be created, edited and deleted, and any row can be opened as a page. Columns are typed on creation, and a column’s type can be changed subsequently, so a field that began as free text can become a fixed set of choices once its vocabulary is established.

In the table view, rows and columns are reordered by dragging. Hovering over a row displays its handle in the margin to the left of the table, level with that row. Dragging the handle moves the row; selecting it opens that row’s actions. The row’s grip and ⋮ menu remain at the end of the row. A column’s grip is in its header.

Rows can be dragged only while the table is in manual order. Once a sort or grouping is applied the order is determined by that, and the handle is not offered. Dragging a column moves it within that view alone where the view carries its own column order, and across the whole database otherwise. Column widths are dragged from the edge of a header and are retained per view.

The row handle’s menu also moves a row one position up or down and inserts a new row directly above or below it. These are the same positional edits as dragging, for use where the table is long enough to make dragging impractical. They are subject to the same manual-order condition.

Relations warrant planning in advance: they link to another database, and lookups and rollups read across that link. Establishing the relation correctly allows the derived columns to follow; adding it later requires re-entering values already held.

Something wrong on this page? Report it