How do i use a database note?

[DuckersMcQuack]

I want to make a table note where there's a red cell with a X in it, when clicked, it turns green with a checkmark, and i want to have a database note for that, but i couldn't figure out how to make that sql/sqlite-trilium note type properly for the table-note to write each cell's state into said database note. How do i properly set it up to do this? As i'm setting up a fancy table structure for each pokemon card series's sets and sub-sets, so it needs a database of sorts so i can properly update the lists with convenient clicks

And what's the difference between sql and sqlite-trilium? The SQL note would just be a "middle man" for a actual SQL docker that stores the states for instance?

[dosubot[bot]]

Great question — the two SQL-related note types serve very different purposes:

SQL vs. SQLite (Trilium)

• A SQL code note (MIME text/x-sql) is just a syntax-highlighted text file. It doesn't execute anything — it's for storing SQL snippets as documentation or reference [1].
• A SQLite (Trilium) code note (MIME text/x-sqlite;schema=trilium) is an executable SQL console that runs queries directly against Trilium's own internal SQLite database [2]. When you hit "Run," it actually executes the SQL — both reads and writes. This requires the sqlConsoleEnabled security setting to be turned on [3]. So to your question: no, the SQL note is not a middleman for an external Docker SQL server — it's purely a code-highlighting note type. The SQLite (Trilium) note talks directly to Trilium's built-in database.

For your Pokémon card tracker, though, you probably don't want raw SQL notes. A better approach is to use a render note + a script note that stores per-cell state as JSON in a regular note's content:

1. Create a note to hold your state — its content would be JSON like {"set1:card5": true, "set2:card3": false}.
2. Create a JS Frontend code note containing the script that builds your table, reads the state JSON, renders red ✗ / green ✓ cells, and toggles + persists state on click.
3. Create a render note and link it to your script note via a ~renderNote relation [4].

The script would read and write state using api.runOnBackend() to call note.getContent() / note.setContent() on the state note [5]. This keeps everything inside Trilium with no external database needed.

A rough script pattern:

// In your render script
const stateNoteId = "YOUR_STATE_NOTE_ID";

// Read state from backend
const stateJson = await api.runOnBackend((id) => {
    return api.getNote(id).getContent();
}, [stateNoteId]);

const state = JSON.parse(stateJson || "{}");

// Build table, render cells based on state...
// On cell click, toggle state and persist:
async function toggleCell(key) {
    state[key] = !state[key];
    await api.runOnBackend((id, newState) => {
        api.getNote(id).setContent(JSON.stringify(newState));
    }, [stateNoteId, state]);
    // Re-render the cell UI
}

This approach gives you clickable toggling cells that persist across page loads, all within Trilium. The render note system supports full HTML/JS/CSS so you have complete control over the table styling [6].

To reply, just mention @dosu.

---

Docs are dead. Just use Dosu.

[eliandoran]

@DuckersMcQuack , why not use the Table collection? You can use a boolean promoted attribute, no scripting or database management required.