WhoDB

Establishes connections to SQL (PostgreSQL, MySQL, SQLite), NoSQL (MongoDB, Redis), Graph (Neo4j), and object databases through a unified connection abstraction layer. The CLI parses connection strings, manages authentication credentials, and automatically introspects database schemas to build an in-memory representation of tables, collections, indexes, and relationships without requiring manual schema definition.

Accepts natural language questions about data and converts them to database-specific query syntax (SQL, MongoDB query language, Cypher, etc.) using an LLM backend. The system provides the LLM with the introspected schema context, executes the generated query against the connected database, and returns results with optional explanation of the query logic. Supports multi-turn conversation to refine queries iteratively.

Supports writing shell scripts or CLI commands that execute templated queries with variable substitution, conditional logic, and output formatting. Enables automation of repetitive database tasks (backups, data exports, cleanup jobs) without writing application code. Integrates with standard Unix pipes and redirection for composability with other tools.

Displays query results in a paginated, interactive TUI (terminal user interface) with column sorting, row filtering, and data type-aware formatting. Supports exporting results to CSV, JSON, or other formats. Implements keyboard navigation and search across result sets without requiring additional tools or context switching.

Translates queries between database-specific syntaxes or executes queries written in a normalized intermediate format across different database types. For example, a single query structure can be executed against PostgreSQL, MongoDB, and Neo4j with automatic syntax adaptation. Uses a query abstraction layer that maps common operations (filter, project, join, aggregate) to database-native implementations.

Stores and manages database connection profiles (credentials, connection strings, authentication methods) in a local encrypted or plaintext configuration file. Supports quick switching between saved connections via CLI flags or interactive selection. Implements credential management patterns to avoid hardcoding secrets in command history or shell scripts.

Watches connected databases for schema changes, new tables/collections, or data modifications and alerts the user via CLI notifications or logs. Implements polling or event-based monitoring depending on database capabilities (e.g., PostgreSQL LISTEN/NOTIFY, MongoDB change streams, Redis keyspace notifications). Tracks changes over time with optional historical logging.

Imports data from CSV, JSON, Parquet, or other formats into connected databases with automatic type inference and schema mapping. Supports batch inserts, upserts, and conflict resolution strategies. Implements streaming for large files to avoid memory exhaustion and provides progress tracking and error reporting for failed records.

Maintains a searchable history of executed queries with timestamps and results metadata. Allows users to save frequently-used queries with names and descriptions, organize them into collections, and re-execute with parameter substitution. Implements full-text search over query history and saved queries for quick retrieval.

Generates summary statistics (count, min, max, average, percentiles) for numeric columns and frequency distributions for categorical data. Provides simple ASCII-based visualizations (histograms, bar charts) in the terminal or exports data for external visualization tools. Supports aggregation and grouping to create pivot-like summaries.

Compares schemas or data between two connected databases and generates a diff report highlighting additions, deletions, and modifications. Supports schema-only comparison (table/collection structure) or full data comparison with row-level diffs. Useful for validating migrations, replication, or backup integrity. Generates migration scripts or sync commands to reconcile differences.