sqlite-inspector

Compare REST API results with MikoPBX SQLite database tables to identify data integrity gaps.

569|85|Updated Jun 7, 2019

Search Tags:#database #verification #sqlite #integrity #CDR

Ready to run

npx skills add https://github.com/mikopbx/Core --skill sqlite-inspector

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sqlite-inspector
Source: https://github.com/mikopbx/Core/tree/main/.claude/skills/sqlite-inspector
Command: npx skills add https://github.com/mikopbx/Core --skill sqlite-inspector

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires docker, sqlite3, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Quick verification of data consistency in SQLite databases and referential integrity after REST API operations.

Core Features & Use Cases

Verifies REST API results persist correctly in the database
Validates foreign keys and relationships
Inspects CDR data for routing verification
Debugs data issues at the database level

Quick Start

Use docker exec to query /cf/conf/mikopbx.db and/or CDR databases; supports multiple output formats.

Frequently Asked Questions about sqlite-inspector

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I verify SQLite database integrity after REST API operations?▼

Database integrity verification compares REST API results against your SQLite database to catch data consistency gaps. Query the MikoPBX database using docker exec with sqlite3 to inspect tables like m_Extensions, m_Sip, m_Providers, and CDR records, then cross-reference API responses to identify mismatches or missing data.

Can I validate foreign keys and referential integrity in a Docker SQLite database?▼

Yes. Run sqlite3 queries inside your Docker container against /cf/conf/mikopbx.db to inspect foreign key relationships across m_Extensions, m_Sip, m_Providers, m_IncomingRoutingTable, m_OutgoingRoutingTable, and m_CallQueues. This reveals broken references and orphaned records.

What's the best way to debug CDR data consistency in MikoPBX?▼

Query the cdr_general and cdr tables directly via docker exec and sqlite3 to inspect call records for routing accuracy and data gaps. Compare results with API endpoints to identify where CDR entries diverge from expected state.

Do I need Docker and sqlite3 to inspect MikoPBX databases?▼

Yes. The Skill requires both docker and sqlite3 to execute queries inside your MikoPBX container and access the /cf/conf/mikopbx.db file. These are listed as core dependencies for running database verification.

How do I output database query results in multiple formats?▼

The Skill supports multiple output formats when querying SQLite databases via docker exec. Specify your preferred format (e.g., CSV, JSON, or table) in the sqlite3 command to tailor results for downstream analysis or reporting.

When should I verify database consistency instead of relying on API logs?▼

Verify database consistency when API operations complete but you suspect data didn't persist correctly, when debugging foreign key violations, or during testing to confirm that database state matches expected API outcomes before deployment.