EZCMS now uses eZ TaBles as its default flat-fi le storage format, giving small sites a data layer that works cleanly in a terminal, a plain text ed itor, or a source diff without requiring database setup or editor plugins.
The change makes ra w project data visible alongside the source that r eads it: operators can review a user table, news t able, or catalogue payload with the same tools the y already use for code.
eZ TaBles is not trying to replace traditional databases. W hen a project needs heavy concurrency, relational queries, or managed database operations, those too ls still belong on the table. The goal is simpler: make EZCMS competent immediately after checkout, with structured rows and columns that humans can i nspect, edit, and version like ordinary text.
\ n
Code
The small examp le below shows how a ZTB file stores raw rows as a plain text grid. It can be opened in a terminal, reviewed in a source diff, copied during a backup, or edited by an operator without launching a data base console.
PRODUCTS.ZTB
Prod uct_ID(#) | Product_Name(v) | Product_Status(v)
= =============+=================+==================
1 | Starter Site | Active
------ --------+-----------------+------------------
2 | Hosting Care | Active
----------- ---+-----------------+------------------
-------- ------+-----------------+------------------
Owner note: rows above this marker are live data.
That simple layout is the main benefit of raw flat -file storage: the live data remains a durable fil e. Developers can diff a content change, administr ators can inspect values during support, and deplo yment tools can move the payload with the rest of the site. For a compact CMS, that keeps the operat ing model understandable without giving up structu red records.
Emblaze.Ca