Explore, query, and edit Harper data from Tabularis.
This driver connects Tabularis to a Harper instance through Harper's HTTP Operations API. It brings Harper databases and tables into the Tabularis explorer while preserving Harper's flexible document model.
Harper is an all-in-one backend that combines a database, caching, application hosting, and messaging in a single runtime. Its database provides ACID-compliant storage, flexible schemas, automatic and explicit indexing, and access to the same data through several interfaces—including SQL, REST, and Harper applications.
This plugin focuses on the database administration and ad-hoc querying experience. It does not attempt to configure Harper applications, REST resources, messaging, replication, or AI models from Tabularis.
- Browse Harper databases, tables, attributes, primary keys, and per-attribute indexes.
- Inspect heterogeneous documents in Tabularis's data grid, even when records have different fields.
- Run one Harper SQL
SELECT,INSERT,UPDATE, orDELETEstatement at a time. - Insert, update, and delete records directly from the grid.
- Create and drop tables.
- Add untyped (
ANY) attributes to any table and remove attributes from dynamic tables. - Connect over HTTP for trusted local development or HTTPS with publicly trusted certificates.
- Work with Harper v4 and v5 metadata shapes.
Tabularis can display Harper indexes, but it cannot create or drop named, unique, or compound indexes through this plugin. Views, foreign keys, routines, SQL EXPLAIN, full column alterations, custom certificate authorities, and client certificates are not currently exposed.
Adding a column is limited to ANY because Harper's create_attribute operation does not accept a type. Dropping a declared attribute from a schema-defined table is rejected when Harper would retain its stored values. Grid updates and deletes require a supported scalar primary key. See Capabilities and limitations for the complete compatibility notes.
Install Harper from Settings → Available Plugins in Tabularis. If it is not yet listed in your Tabularis version, or you prefer a manual installation, download a bundle from this repository's Releases page.
To connect, provide the Harper host, port, username, and password. An empty host defaults to localhost, and port 9925 is the default. Selecting a database is optional for browsing. When a connection exposes more than one database, choose one explicitly before editing rows or running destructive DDL.
For a local Harper instance using plain HTTP, leave the host empty (or enter localhost or an explicit http:// host) and leave SSL mode unset, or set SSL mode to Disabled. Preferred, Required, and verification modes always use HTTPS. Only disable TLS on a trusted network because Harper credentials are sent with the request.
Harper SQL uses database.table names. Quote identifiers with backticks when they contain special characters or collide with a reserved word:
SELECT *
FROM `data`.`animal`
ORDER BY `name`
LIMIT 100;Write queries must always qualify the target with its database so the plugin cannot apply a change to an unintended database.
Harper recommends SQL for investigation and administration rather than performance-sensitive production access. Applications should use Harper's native application, REST, or NoSQL interfaces where appropriate.
Tabularis starts the harper executable and communicates with it over JSON-RPC on standard input and output. The plugin translates those requests into authenticated HTTP calls to Harper's Operations API; no separate Rust SDK is required.
- Capabilities and limitations
- Development and local installation
- Harper documentation
- Tabularis plugin registry
Licensed under the Apache License 2.0.