Editing one database row safely in phpMyAdmin

Export the affected table or database first. Identify the exact table, primary key and intended value from reliable application documentation. Never select a row merely because it is third in a list; display order is not a stable identifier.

1. Select the correct database and table, then use Browse or Search to locate the record by a unique key.
2. Confirm the surrounding values identify the intended record. Choose Edit for that row rather than a bulk action on the entire table.
3. Change only the required field. Preserve NULL values, encodings and data types, and avoid applying a function unless the application specifically requires it.
4. Save the change, then inspect the row again to confirm the exact result and number of affected records.
5. Test the corresponding application function. If the application caches the setting, clear only the relevant supported cache after verifying the database value.

Suppose your application documentation identifies an account by primary key 42. In a test database with the fictional table and columns shown below, a read first would look like this. Replace the identifiers only after checking your real application schema.

SELECT id, display_name, status
FROM example_accounts
WHERE id = 42;

Confirm the one returned record matches the intended person or object and preserve its original values. If no row appears, verify the selected database and identifier. If the table has no stable unique key, stop and establish a reliable way to identify the record before using a row-edit action.

This SELECT changes nothing. Use the application interface where it can perform the actual update, especially for billing, passwords or structured data. If a supported direct edit is required, change only the documented field and verify the application behaviour afterwards.

The intended record should contain the new value, and unrelated records should remain unchanged. Test the application’s behaviour, not only the phpMyAdmin success notice.

Do not hand-edit serialized or structured application data without a tool that preserves its format. A changed string length can corrupt PHP-serialized values. If the result is wrong, restore the recorded original value or scoped backup before making further changes, especially on a live shop.

• Exporting a recoverable database backup in phpMyAdmin
• Importing a database backup with phpMyAdmin
• Deleting an unused database table with phpMyAdmin
• Can phpMyAdmin repair a damaged database table?

• phpMyAdmin: Intro