phpMyAdmin can change values stored in a database table. This guide covers editing a record, not changing the table's columns or structure. Prefer your application's own settings screen when possible: direct database edits bypass application checks and can break relationships or specially formatted data.
The legacy title refers broadly to editing a table. The written steps cover record values; changing table structure requires a separate application-specific migration plan.
Before you start
- Export the affected table or database and record the original value. Identify the exact database, table, and unique record key before opening an edit form.
- Use a staging copy for unfamiliar changes. Ask the application developer before editing serialized settings, passwords, payment records, or values used by other tables.
Instructions
Open the correct table
In cPanel, open Databases, then phpMyAdmin. Select the full database name and the table containing the record.
Find the intended record
Use Browse or Search to locate it. Compare a primary or other unique key and relevant values so you can distinguish it from similar-looking rows.
Open the record editor
Choose Edit on that row. Check the selected record again. Avoid the table's Structure or Operations controls, which perform different tasks.
Change only the required value
Update the intended field. Keep unrelated fields, function selectors, NULL choices, and identifiers unchanged unless the application's documented procedure requires otherwise.
Save and inspect the result
Click Go or the displayed save action. Read the result, reopen the record, and test the affected application behavior before making additional changes.
Check the result
- Confirm the correct record contains the new value and that unrelated records remain unchanged.
- Check the application itself. If it still shows an old value, investigate its documented cache behavior before editing another record.
Troubleshooting
- Edit is unavailable or phpMyAdmin cannot identify a unique row.
- Stop and ask the developer to identify a safe record key. Do not add a primary key to a live application table solely to make the Edit link appear.
- The application fails after the edit.
- Use the recorded original value or an agreed backup recovery procedure. Avoid further trial-and-error changes, and share the non-sensitive error with your developer or support.
Watch the video
The video may show an older interface. Use the written instructions above when screen names differ.
Continue with a related task
- How to Export a Database Table with phpMyAdmin in cPanel
- How to Import a Database with phpMyAdmin in cPanel
