ArchitectureA supervised JVM-class runtime — OLTP on seven engines, OLAP on three. AI-native, MCP-native, observable as plain SQL.Read the architecture
Está viendo la edición Perú. Está viendo la edición Colombia. You're viewing the Pakistan edition. Cambiar a la edición global →Cambiar a la edición global →Switch to the global edition →

The matrix view: every X against every Y, configured instead of hand-written

A query that returns one row per cell is drawn as a dense grid from its configuration: axes, colour rules, filters, actions on empty cells, and a refresh that re-reads only the lines an action touched.

Some questions are answered by a grid of two lists: which users reach which databases, which roles hold which AI tools. These screens used to be hand-written HTML panels or pivoting scripts. This release adds MATRIX, a view type of a query-backed object, and the access screens were rebuilt on it.

Drawn from configuration

  • One row per cell The statement returns a row key, a column key and a value. The view collects both axes, orders them by label, key, count or group, and limits each one with a counted remainder.
  • Colour and marks A cell is coloured by a value map, by ordered rules or by a scale, and can be faded, hatched or outlined. The access matrices share one vocabulary: coloured means held, outlined means it can be given, a lock means refused, hatched means no access.
  • Filters on the page Pickers and a search narrow the loaded cells in memory. A filter on one axis narrows that axis and leaves the other whole.
  • Turned round A matrix can declare its rotated form, and a button swaps the axes.

Acting on a matrix

  • Heading rows A statement may return a row per line of each axis beside its cells. A user with no grant and a database nobody holds are still drawn, and no row is loaded for an empty pair.
  • Empty-cell actions A cell with no row offers the actions whose rule holds on its two heading rows, so access can be granted from an empty cell without loading every pair. The server is unchanged: the action runs on a heading row with the other heading's columns laid over it.
  • Keyed refresh A matrix that names a refresh key re-reads only the keys an action ran on and merges them by cell identity. On the database access matrix, re-reading one user took 0.57 seconds and 8 KB, where a full reload took about four seconds and 18 MB.
  • Grouped row buttons Row buttons that share a group, such as Grant, Change and Revoke, are drawn as one menu.

The matrix is metadata like any other view: the dictionary holds the statement and the configuration, a schema validates it, and the same object prints. A new "every X against every Y" screen needs no client code.