Learn
Understand Oliphaunt's runtime model before choosing production settings.
Use these pages after the first query works and you need to make production choices: where data lives, which runtime boundary fits, how mobile lifecycle behaves, and how to package the app without extra extension files.
Read by decision
Each page answers one production question after the first query works.
Storage
Root directory, WAL, backup.
Runtime
Direct, broker, server, WASM.
App fit
Mobile, Tauri, SQLite migration.
Embedded PostgreSQL
What does my app own on disk?
Roots, WAL, extensions, lifecycle, backup, and restore live behind SDK APIs.
Native Runtime
Which runtime boundary fits my app?
Direct gives one embedded session, broker adds a helper process, and server gives PostgreSQL client sessions.
Mobile Stability
How does this behave on iOS and Android?
Mobile direct mode covers app storage, foreground/background transitions, relaunch, and WAL recovery.
Moving From SQLite
What changes when I move from one file to PostgreSQL?
Storage, schema features, extension selection, export/import, and package-size checks change first.
Tauri Usage
Where does the database handle live in a Tauri app?
Rust state owns Oliphaunt. The webview calls narrow app commands instead of raw runtime handles.
Suggested Paths
- Mobile apps: Read Embedded PostgreSQL, then Mobile Stability. React Native developers then read the React Native architecture page before wiring background hooks or streaming large protocol responses.
- Desktop apps: Read Native Runtime first. Tauri developers then read Tauri Usage and keep database ownership in Rust state.
- SQLite migration: Read Moving From SQLite, then use Extensions and Performance while sizing the app artifact and benchmark plan.
What Learn Covers
Learn pages explain product behavior in app terms. Use the SDK page when you need install steps and code. Use Reference when you need a matrix, catalog, or version lookup.