Editing Database Data
Work safely with live table rows in Database Manager: open a table, edit values, and understand when changes affect data instead of schema.
Introduction
Section titled “Introduction”Use this workflow when the table structure is already in place and the job is about row content, not columns or relations. Editing data in Database Manager is immediate and practical, but it should be treated differently from schema design because you are changing live records instead of preparing migrations.
Know what kind of change you are making
Section titled “Know what kind of change you are making”The main Database Manager tree is where both schema work and data work begin. Before opening an editor, decide whether you need to redesign the table itself or simply correct its current rows. That distinction prevents a common mistake: editing live data while thinking you are still in a safe schema-design phase.
Open the table data editor from the table you trust
Section titled “Open the table data editor from the table you trust”The usual entry point is the table itself. Open View/Edit Data on the table you want to inspect, and verify that you are on the intended connection or target first. This keeps the workflow concrete: choose a real table, open its rows, and work directly on the records that power your app.
What the row editor is for
Section titled “What the row editor is for”Treat the data editor as a live records workspace. It is strong for checking seeded content, correcting wrong values, reviewing foreign-key results, and confirming what your forms or API actions really stored. It is not the place to redesign table shape, rename fields, or rethink relations.
Refresh before you trust what you see
Section titled “Refresh before you trust what you see”If schema or data changed outside the current session, refresh first so the manager reflects the database accurately. This is especially important when you switch branches, pull teammate changes, or apply migrations elsewhere. A quick refresh reduces the chance of editing against stale assumptions.
Next steps
Section titled “Next steps”Continue with related Database Manager workflows once row editing makes sense: model nested data with sub tables, create many-to-many structures with multi references, or follow the database action tours to see how edited data is queried and updated in Server Connect.