Database Reference (.base)

Last reviewed: 2026-11-03

This page lists everything a .base file can contain and what Plainva does with each part: every top-level key, every filter form, every view type with its options, summaries, sorting, limits, what happens to keys Plainva does not know, and where Plainva behaves differently from Obsidian Bases. It describes what Plainva’s code reads, evaluates and writes today — not Obsidian’s documentation.

For everyday use, read Databases (.base) first. The rules a tool must keep when it writes vault files directly, and the full relation example, are in the File Format Reference.

At a glance

Part of the fileWhat Plainva does
filtersReads and applies the sources (folder, tag) and the conditions listed under Filters
viewsReads all eight view types, their order, sort, filters and summaries
propertiesReads the column schema, the display name and Plainva’s plainva block
summaries (view)Computes the fourteen built-in summaries
formulasKeeps them in the file, does not compute them
summaries (top level)Keeps custom summary formulas, does not compute them
thisNot supported yet
Other keysKeeps them in the file (see Keys Plainva does not know)

Top-level keys

A .base file is YAML with these top-level keys. All of them are optional; a file without views opens with one table.

KeyContentIn Plainva
filtersWhich notes belong to the database (sources)Read and applied
propertiesOne entry per column, keyed by the property idRead; Plainva’s additions live in its plainva block
viewsThe list of viewsRead; every view needs a name
formulasObsidian formulas, name: expressionKept unchanged, not computed
summariesObsidian custom summary formulasKept unchanged, not computed

Plainva never writes another top-level key: Obsidian refuses to open a .base with a key it does not know. A top-level columns: key written by very old Plainva versions is still read and moved into properties the next time the file is saved.

Properties (properties)

Property ids

A property id names a column. Three kinds exist:

IdMeansExample
note.<key>A key of the notes’ frontmatternote.status
file.<field>A fact about the file (see File fields)file.mtime
formula.<name>An Obsidian formula from formulasformula.price_per_unit

The keys of properties, a view’s order and sort[].property use these ids. Inside a filter expression and inside a plainva block a frontmatter key is written bare (status); a filter expression understands note.status as well.

When a note writes a key in a different case than the column (Due against the column due), Plainva still shows the value in that column and writes changes back under the note’s own spelling.

Display name

properties.<id>.displayName is Obsidian’s column label. Plainva shows it as the column header and keeps it. Without it a frontmatter key is shown with a capital first letter (on screen only); the file fields have their own names, for example Name, Modified, Size, Path, Checklist and Day from the file name.

The plainva block of a column

Everything Plainva adds to a column lives under properties.<id>.plainva. Obsidian ignores it.

KeyValueMeaning
inputa field type (list below)The column’s field type
ratingMaxnumber, 1 to 10How many marks a rating has (default 5)
ratingGlyphone characterThe mark a rating draws (default a dot)
optionslist of optionsFixed values for select, status and multi-select
relationBasevault-relative .base pathThe database a relation points into
relationLimitoneA relation holds exactly one link; absent means no limit
reverseOf{ base, property }A computed reverse-relation column
rollup{ through, of, fn, where }A computed rollup column (see Rollups)
previousKeyslist of up to 8 former namesLets comments find a renamed column again

Field types (input)

text, number, rating, checkbox, date, datetime, select, status, multiselect, list, tags, url, email, phone, relation.

Two older spellings are read as well: multi-select as multiselect, and link as relation. A column without input — or with a value not in this list — gets its type from the values in the notes: true/false is a checkbox, a number a number, a list of [[links]] a relation, 2026-07-03 a date, a web address a URL, and so on. A reverse-relation column and a rollup column have no input.

Options and colours

An option is { value, label, color, group }; only value is required. color is one of the palette names gray, teal, blue, green, amber, coral, purple, pink — an unknown name falls back to a colour derived from the value. group is used by Status only: options with the same group form a stage. A plain string is read as an option with that value.

Rollups

A rollup column computes a value from the notes a link column of this database points at. The value is stored in no file.

A rollup that misses a required part, or names a function not in this list, is ignored: the column stays empty and the database still opens. A rollup through another computed column stays empty too.

File fields (file.*)

These values come from the file, not from its frontmatter. Each row of a database carries the following:

FieldValue
file.nameThe note’s title property if it has one, otherwise the file name without .md
file.pathThe vault-relative path
file.mtimeLast modified, in milliseconds
file.ctimeCreated, in milliseconds, where the file system reports it
file.sizeSize in bytes
file.tagsAll tags of the note, frontmatter and text, each with #; filled when a filter, a pinboard or a view that shows or sorts by the column needs them
file.tasksCheckbox progress as done/total; filled for boards and for a view that shows the column
file.dayThe day a daily note’s file name stands for, by the vault’s folder and format; read-only, and only the date field of a calendar or timeline can use it
file.revisionAn internal change marker; do not rely on it

file.folder works as a source (see Sources) but is no column. file.basename, file.ext, file.links, file.backlinks, file.embeds, file.properties and file.file are not provided: a column with one of them stays empty, and a filter reads them as empty.

Filters

Where filters live

The top-level filters holds the sources — which notes belong to the database. Every view can carry its own filters with conditions that narrow that view only; Plainva writes the conditions there. Both levels apply together. Conditions a file keeps at the top level still work; the next save in Plainva moves them into each view.

Sources

SourceExpression
Folderfile.folder == "Projects/Active" — the folder and all its subfolders; "" and "/" are the whole vault
Tagfile.hasTag("project") — the note carries exactly this tag; a leading # is ignored

Several sources combine with and or or like any other condition. A database without sources contains every note of the vault. Attachments, the reserved index.md and log.md, and files or folders whose name starts with a dot are never rows.

Conditions

A condition is a string. Values are in double quotes; \" and \\ escape a quote and a backslash. The property is written bare or with note..

ConditionExpression
isstatus == "Done"
is notstatus != "Done"
containscontains(labels, "urgent") or labels.contains("urgent")
does not contain!contains(labels, "urgent") or !labels.contains("urgent")
greater than, less thaneffort > "3", effort < "8"
at least, at mostdue >= "2026-07-01", due <= "2026-07-31"
is emptystatus == "" or status.isEmpty()
is not emptystatus != "" or !status.isEmpty()
has a tagfile.tags.contains("#work"), negated with !
header colour, iconnote.plainva.header_color == "#2a7f7b", note.plainva.icon == "lucide:pin"

How values compare

and, or, not

A filters object has exactly one of and, or and not on each level; its entries are condition strings or further filter objects.

KeyMatches when
andevery entry matches
orat least one entry matches
notno entry matches

Plainva evaluates any depth. The filter panel edits one level of groups under All or Any (Add group); a deeper structure appears as Complex filter (not editable), stays in the file and is applied — a condition inside it that Plainva cannot read is named below it as not applied. An older file with and and or side by side on one level is read as “all of and and one of or” and written in the valid form on the next save.

What Plainva cannot read

Only the forms in the two tables above are understood. Anything else — file.inFolder(…), file.hasLink(…), file.hasProperty(…), a number without quotes (price > 2), && and || inside one string, arithmetic, date functions such as now(), or this — stays in the file and is shown in the filter panel as written, with the note Not applied: Plainva cannot read this condition, so it filters nothing. The view then shows more notes than the same filter does in Obsidian.

Formulas

Plainva does not compute Obsidian formulas. formulas stays in the file unchanged, and a formula.<name> column in a view’s order is shown without values. Export table → Formulas (.base) writes some rollups as formulas so that Obsidian can compute them (see Databases).

Views

Keys of every view

KeyValueIn Plainva
typetable, list, cardsThe view type; see the next table
nametextRequired; Plainva gives a view without one a name when it saves
orderlist of property idsThe visible columns, in this order
sortlist of { property, direction }Sort rules, ASC or DESC
filtersfilter objectThe view’s own conditions
summariesmap of property id → summary nameThe footer of each column
plainvamapPlainva’s view options, below

The eight view types

Obsidian knows table, list and cards. Plainva’s other view types are stored as type: table plus plainva.render, so Obsidian shows them as a table.

View typetype on diskplainva.render
Table (table)table—
List (list)list—
Gallery (gallery)cards—
Board (board)tableboard
Calendar (calendar)tablecalendar
Timeline (timeline)tabletimeline
Graph (graph)tablegraph
Pinboard (pinboard)tablepinboard

Board, Calendar, Timeline, Graph and Pinboard are offered as a View type only while Allow Plainva extensions for .base files is on. A type Plainva does not know is shown as a table and stays in the file as written until you choose another View type.

View options (views[i].plainva)

Inside the plainva block a property is written bare (status), not as note.status.

KeyView typesValue
renderBoard, Calendar, Timeline, Graph, PinboardThe view type, see above
groupByBoardThe property the columns are made of; without it, the property of Obsidian’s own groupBy of the view
boardLaneByBoardA second property for Swimlanes by
boardWipLimitsBoardMap of column value → most cards (WIP limit), whole numbers above 0
boardColorModeBoardcolumn tints the whole column; absent = only the header chip
boardColumnOrderBoardManual column order; __UNGROUPED__ is the column without a value
colorByBoard, TimelineCards and bars take this property’s option colour (Colour by)
dateFieldCalendar, TimelineThe start date (Date field, Start date); a date property or file.day
endFieldCalendar, TimelineThe End date
coverImageGalleryThe property holding the Cover image
subItemsPropertyTableThe parent relation for Sub-items
widthsTableMap of column → width in pixels
dateFormatalllong, iso or relative; absent = the default short form
graphEdgesGraphRelation properties drawn as edges
graphColorByGraphA select or status property that colours the nodes
graphSizeByGraphA number property that sizes the nodes
graphShowExternalGraphtrue also shows link targets outside the view
graphShowIncomingGraphtrue also shows links coming in from other databases
pinboardOrderPinboardPaths of the unpinned cards, in manual order
pinboardPinnedPinboardPaths of the pinned cards, in order
pinboardFilterByPinboardLabel source: a multi-select property; absent = tags

File-wide options (first view only)

These keys belong to the whole database. Plainva writes them into the plainva block of the first view only and reads the first valid value of each.

KeyValue
fileIconColorHex colour of the database icon (Database icon color)
newItemFolderFolder where Entry stores new entries
newItemTemplateTemplate for new entries
contextFiltersProperties that limit an embedded database to the note it is embedded in (This note)
taskListAccount and list ("<account id> <list id>") a new task is also created in

Summaries

views[i].summaries maps a column to one of these names; the footer computes it over the rows the view shows.

NameIn PlainvaResult
AverageAverageMean of the numbers
MinMinSmallest number
MaxMaxLargest number
SumSumTotal of the numbers
RangeRangeLargest minus smallest number; for dates the span in days
MedianMedianMiddle value of the numbers
StddevStd devStandard deviation of all numbers (population)
EarliestEarliestEarliest date
LatestLatestLatest date
CheckedCheckedRows whose value is true or yes
UncheckedUncheckedAll other rows
EmptyEmptyRows without a value
FilledFilledRows with a value
UniqueUniqueNumber of different values; list entries count one by one

Numbers are rounded to two decimals, and a decimal comma is read as well. A column without a usable value shows no footer rather than 0. Any other name is a custom formula from the top-level summaries: Plainva keeps it and shows Custom: … in the menu, but computes no value.

Sorting and grouping

Embedding a database, and this

![[Projects.base]] in a note shows the database inside the note, in reading view and in the editor. A part after # (a view name, as in ![[Projects.base#Board]]) is ignored: the embed shows the view last used for this database. A ```base code block in a note is shown as code, not as a database.

this is not supported yet. A filter or formula that uses this stays in the file, but Plainva does not evaluate it. Two things cover the most common case, “show the entries that belong to this note”: contextFilters (This note in the filter panel) limits an embedded database to the note it is embedded in through a relation property, and an embedded database that relates to the database of its host note offers Filter this database to the current note by itself. Both act only inside Plainva; Obsidian shows all rows.

Limits

Keys Plainva does not know

Plainva reads a .base, changes only what you changed in the app, and writes the whole file anew — as YAML with LF line endings and without a BOM, so comments and the spacing of a hand-written file are not kept. Of what it does not know:

Differences to Obsidian Bases

TopicObsidianPlainva
Formulas, custom summariesComputedKept, not computed
thisSupportedNot supported yet
Filter expressionsThe full expression languageThe forms in Conditions
file.folder == "X"Only notes directly in XX and all its subfolders
file.hasTag("x")Also #x/childExactly #x
file.nameThe file nameThe title property if the note has one
View limit, groupByAppliedlimit kept, not applied; groupBy groups a board, not a table
View typestable, list, cards and plugin typesEight types; an unknown one is shown as a table and kept in the file
![[db.base#View]]Opens that viewThe view last used
```base code blockA databaseA code block
Plainva’s plainva blocksIgnoredBoard, calendar, timeline, graph, pinboard, relations, rollups, field types

See also