Tables and Safe Editing

Tables and Safe Editing

The table viewer provides server-side pagination, multi-column sorting, parameterized filters, search, column metadata, indexes, foreign keys and DDL.

Buffered changes

Edit, insert, duplicate or mark rows for deletion. Changes stay in a local buffer until you select Apply, so you can inspect the summary and generated SQL or discard the whole batch.

Pending rows are deliberately easy to distinguish: edited rows are yellow, new rows are green and rows marked for deletion are red. A duplicated row initially appears directly below its source; after Apply, the database may place it elsewhere according to generated keys and the active sort.

Large and structured values

Double-click a large editable cell to open the full-value editor. Choose Plain text, JSON or HTML, then use Check before saving. Valid JSON and HTML show a positive status; malformed structured content stays open with a precise error. HTML is validated as source text and is never rendered or executed by LakeDB.

Safe row identity

Editing is enabled only when LakeDB can identify exactly one row through a primary key or a complete UNIQUE index without nullable columns. Otherwise the table remains read-only.

Conflict detection and rollback

LakeDB starts a transaction, locks each target row and compares its original values. If another user changed it, or a mutation affects anything other than one row, the complete batch is rolled back and the local buffer remains available for review.

Read-only connections block writes and DDL. Dangerous production changes require typing PRODUCTION (legacy Spanish installations also accept PRODUCCION).