Skip to content

A database with SQLite diagrams ​

A database with SQLite

Start with how the application begins, then follow data between its folders. Open an operation to see its decisions, calls, failures and cleanup. Its explanation supplies the exact contract and linked dependencies.

This view includes 2 application source files. Package and interface boundaries show checked contracts; their runtime implementations are not expanded. The views describe the checked program, not desired requirements or a recorded execution.

Where execution begins ​

Startup ​

It prints storedName. If this work raises SqliteError as error, it prints error.message. source

Data flow ​

100%
Mermaid source
flowchart TD
    n0["database"]
    n1["Startup"]
    n1 -->|"storedName → string"| n0

Package boundaries ​

database package calls
100%
Mermaid source
flowchart LR
    n0["database"]
    n1["@greenpandastudios/aug-sqlite"]
    n0 -->|"execute(database, sql, …) / openMemory + 1 more → int / own Database + 1 more"| n1

Follow the data ​

Each row opens the complete operations and call sites behind one pair of logical units. A grouped arrow records calls between those units; connected arrows need not belong to the same execution path.

FromToOperationsRead
database@greenpandastudios/aug-sqlite3Inputs, results and call sites
Startupdatabase1Inputs, results and call sites

Data crossing these boundaries (4 contracts) ​

database → @greenpandastudios/aug-sqlite ​

3 operations, 4 sites

execute

Inputs: database: borrow Database, sql: string, parameters: List<string>. Result: int.

Caller or entryEvidence
storedNameCall site · Caller explanation
storedNameCall site · Caller explanation

openMemory

No caller-supplied inputs. Result: own Database.

Caller or entryEvidence
storedNameCall site · Caller explanation

queryScalar

Inputs: database: Database, sql: string, parameters: List<string>. Result: string.

Caller or entryEvidence
storedNameCall site · Caller explanation

Startup → database ​

1 operation, 1 site

storedName

No caller-supplied inputs. Result: string.

Caller or entryEvidence
StartupCall site · Caller explanation

Open a module ​

ModuleRead
database.augFlow and sequences · Explanation
main.augFlow and sequences · Explanation

These are static call boundaries, not a request trace. Interface implementations and foreign internals stop at their checked contracts. Dotted arrows defer a callback or browser action. Imports alone do not imply a call.

Last updated:

The world runs on language