mq-db 0.1.13

Markdown-specialized embedded database with interval-indexed block storage and hierarchical query support
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35

# Virtual Schema

The SQL engine exposes two virtual tables backed directly by the in-memory store — there is no separate schema to migrate.

```sql
SELECT id, path, title, tags FROM documents;

SELECT id, document_id, block_type, content, pre, post,
       depth, lang, properties FROM blocks;
```

## `documents`

| Column | Type | Description |
| --- | --- | --- |
| `id` | integer | Document ID (matches `blocks.document_id`) |
| `path` | text | Source file path, or `NULL` for in-memory-only documents |
| `title` | text | Front-matter / first-heading title, if any |
| `tags` | text | Front-matter tags, comma-joined |

## `blocks`

| Column | Type | Description |
| --- | --- | --- |
| `id` | integer | Block ID |
| `document_id` | integer | Owning document ID |
| `block_type` | text | `'heading'`, `'paragraph'`, `'code'`, `'list'`, `'blockquote'`, `'table_cell'`, `'table_row'`, `'table_align'`, `'yaml'`, `'toml'`, `'html'`, `'horizontal_rule'`, `'math'`, `'definition'`, `'footnote'` |
| `content` | text | Raw block content |
| `pre` | integer | Interval-index pre-order boundary |
| `post` | integer | Interval-index post-order boundary |
| `depth` | integer | Heading depth (`1`–`6`); `NULL`/`0` for non-headings |
| `lang` | text | Code fence language, when `block_type = 'code'` |
| `properties` | text | Remaining block-type-specific properties as JSON |

`pre`/`post` are the Nested-Set interval-index boundaries described in [Index Layers](index-layers.md) — they encode heading hierarchy as a pure integer range, which is what the [`under()`](sql-functions.md) function operates on.