# Sqlitecpp Troubleshooting

> Sqlitecpp Troubleshooting is an Agent Skill for testing & quality published in the SRombauts/SQLiteCpp repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Diagnose SQLiteCpp build, linker, compiler, and sqlite3 integration issues.

- Skill name: `sqlitecpp-troubleshooting`
- Category: [Testing & Quality](https://www.openparable.com/skill/testing-quality/1)
- Source: https://github.com/SRombauts/SQLiteCpp/blob/HEAD/.claude/skills/sqlitecpp-troubleshooting/SKILL.md
- Repository: SRombauts/SQLiteCpp (2,757 GitHub stars when collected)

## SKILL.md

# SQLiteCpp Troubleshooting

## Common compiler errors
- MSVC: `error C2065` or `C2039` usually means a missing include or wrong symbol.
- GCC/Clang: `use of undeclared identifier` or `no member named` indicates missing includes or API mismatch.

## Common linker errors
- `LNK2019 unresolved external symbol "SQLite::Database::exec"`:
  - Missing SQLiteCpp library or missing source file in build.

## Missing sqlite3 on Linux
- Errors like `undefined reference to sqlite3_xxx`:
  - Install `libsqlite3-dev`, or enable internal sqlite3.
  - CMake option: `-DSQLITECPP_INTERNAL_SQLITE=ON`.

## Column metadata error
- `undefined reference to sqlite3_column_origin_name`:
  - Your sqlite3 library lacks `SQLITE_ENABLE_COLUMN_METADATA`.
  - Options:
    - Rebuild sqlite3 with that flag.
    - Disable `SQLITE_ENABLE_COLUMN_METADATA`.
    - Use internal sqlite3 (`SQLITECPP_INTERNAL_SQLITE=ON`).

## Destructors and assertions
- Do not throw in destructors; use `SQLITECPP_ASSERT()` instead.

---

Source: https://www.openparable.com/skill/testing-quality/sqlitecpp-troubleshooting (OpenParable). Cite the canonical URL above.
