DBX4 Data Studio: An Interactive Demo of a Database Built From Scratch

TechnoPKG now runs an interactive demo of DBX4 — a database engine written from scratch in C/C++ — at /dbx4. You can add, edit, delete and bulk-load real rows and watch the engine keep its own audit trail.

Why bother writing a database?

Not to replace Postgres. DBX4 exists to explore one idea properly: what if the engine knew what a table was for? An ERP row isn't just data — it's something that must be traceable, attributable, and connected to other rows. Most databases make you build all of that yourself, in application code, over and over.

What you can do in the Studio

• Browse the demo tables with a live filter box
• Add / update / delete rows through forms — no SQL required
• Bulk insert, update and delete from a JSON block (up to 1000 rows a request)
• Upload an image straight into a BLOB column and preview it back
• Edit XML and CLOB documents in place, alongside ordinary columns
• Inspect the audit trail — every row shows who created it, who changed it, when, and

which login session did it

The part worth looking at

Create a row. Then look at the Audit tab. You never typed a created_by, and the portal never wrote one — the engine did:

| id | created_by | created_at          | updated_by | updated_at          | event_id                   |
| 1  | jsmith     | 2026-07-15 04:00:58 | jsmith     | 2026-07-15 04:01:02 | EV-20260715040102-jsmith-1 |

Note created_at stays frozen at 04:00:58 while updated_at moves. And event_id ties the change to a specific login session — so "what did that sitting touch?" is a query, not an investigation. There is a companion post on how that works.

Rich types are not an afterthought

The demo_doc table holds a title (TEXT), a document body (CLOB), metadata (XML), artwork (BLOB) and tags (OBJECT/JSON) — in one table, with the same audit columns as everything else. Upload a PNG in the Images tab and it comes straight back out.

Access

The Studio writes to a live database, so it follows the same rule as the ERP modules: signed in and approved. Ask for the dbx4 permission if you'd like to try it.

Honest limits

It's a demo, and the guard rails are deliberate: only demo_* tables are editable, UPDATE/DELETE without a WHERE are refused, bulk is capped at 1000 rows, images at 2 MB, and DDL/user-management statements are blocked outright. The engine runs as its own sandboxed service on localhost — the portal never touches the database files.

Comments (0)