Summary
Table Browser opens every table with a primary key straight into editing: the edit toolbar (Add Row / Delete Row / Save Changes) is shown and any cell becomes editable on double-click. Users who only want to look at data are disoriented and can stage edits by accident, which then triggers "Unsaved changes" prompts when switching tables.
Scope
- Open tables in view mode: no staging buffer, no edit toolbar, cells not editable.
- An explicit Edit button in the table header (and a shortcut) turns on edit mode; it shows the existing edit toolbar. When editing is not possible (view, no primary key, read-only session, schema unavailable) the button is disabled with the reason as tooltip.
- Done leaves edit mode (asks to discard pending edits if any). Save / Revert keep edit mode on.
- Switching to another table always starts in view mode again.
- Same behaviour in the PostgreSQL, MySQL, SQLite and extension Table Browsers.
Summary
Table Browser opens every table with a primary key straight into editing: the edit toolbar (Add Row / Delete Row / Save Changes) is shown and any cell becomes editable on double-click. Users who only want to look at data are disoriented and can stage edits by accident, which then triggers "Unsaved changes" prompts when switching tables.
Scope