About Wisdombase
About Wisdombase
A document-oriented data platform that stores and manages project and layer data for WisdomEra applications.
A document-oriented data platform that stores and manages project and layer data for WisdomEra applications.
Each record is an independent document carrying its fields and nested lists together. Related information can therefore be read and updated as one unit.
Similar documents are grouped in table-like layers. Layer parameters define fields, options, and queryable values.
An SQL-like language selects fields, filters by conditions, counts, orders, and pages records in the selected layer.
Queryable parameter values are indexed in the background. New or changed records may pass through a queue, so very recent changes can take a short time to appear in queries.
Database units, domains, and visible applications are configured within project boundaries. Users operate only on authorized units and layers.
A database unit is the management boundary for related layers and documents. Expand it to view and select a target layer.
The layer code is the technical identifier and the layer name is the display label. After selection, all tabs operate on the same target.
Shows layer records in pages. Locate records by key, label, client ID, or update time.
Displays WDMR documents and details; create, update, and rule-based listing actions depend on authorization.
Shows field definitions, data types, and options. Changes affect the data contract used to write and query this layer.
Runs an SQL-like query on the selected layer. Codes can be used directly; names are enclosed in square brackets. LIMIT defaults to 100 and the server returns at most 500 results.
Contains data and backup maintenance actions. Verify the selected unit and layer before clearing data or removing backups.
Combines request traffic, disk and RAM usage, compaction state, and parameter-index readiness for the selected server.
Provides a quick overview of disk usage, index RAM, cached rows, compaction, recent requests, and the index queue.
Shows the most requested services and state, layer, start time, and segments of active compaction.
Shows pending, ready, processing, writing, and failed queue jobs together with ready-layer and indexed-record totals.
Shows engine, readiness, record and parameter counts, progress, disk size, and last indexed time per layer. Rebuild can target one or all layers.
Compares disk, RAM-index rows, request count, and compaction metrics by layer. Outside index cache means unavailable measurement, not zero records.
Opens the SQL-like editor after selecting a database unit and layer. Results appear in a table and wide tables can be viewed fullscreen.
Determines the data boundary for the query. Changing the unit resets layer selection to prevent querying a layer from the previous unit.
Selects the target layer through a searchable control. The editor opens only when both unit and layer are selected.
Used to write, validate, and run queries, view results, and reuse browser-local query history. Clause order is SELECT, FROM, WHERE, ORDER BY, LIMIT, OFFSET. LIMIT defaults to 100 and is capped at 500. Large text values can be output-only and unavailable for filtering.