PHP/HTML/MySQL技术问题：养蜂人注册后无法更新数据库指定行

Hey there! Let's tackle that update problem you're hitting with your beekeeper-focused site. The auto-login flow after registration works, but updating specific rows is failing—this is a super common snag, so let's break down the most likely fixes step by step.

1. First: Verify You're Targeting the Correct Row #

The #1 culprit for failed updates is an incorrect WHERE clause. Here's what to check:

• Ensure you're using a unique identifier: When updating, you need to target a row with a unique value (like a user ID or shop ID stored in your session after login). If you're using a non-unique field (like email without checking for uniqueness), you might be updating the wrong rows—or none at all.
• Debug your session data: If you're using sessions (e.g., PHP's $_SESSION), confirm the ID you're using in the update is actually present. Add a quick debug line like:

  var_dump($_SESSION['shop_id']); // Check if this outputs the correct ID for the logged-in beekeeper
  

• Test your SQL directly: Take the exact update statement you're running (with real values plugged in) and run it in your MySQL client. For example:

  UPDATE shops SET shop_location = 'Apiary #5', phone = '555-1234' WHERE id = 12;
  

  If this works in MySQL but not in your code, the issue is in how your script is passing parameters or handling the query.

2. Check Database Permissions & Field Compatibility #

• Confirm update permissions: Make sure the database user your script is using has UPDATE privileges for the target table. It's rare, but sometimes registration uses a user with write access, but the login/update flow uses a restricted user.
• Match field types: If you're trying to update an integer field with a string value, or a date field with an invalid format, MySQL will silently fail (or throw an error you might not be catching). Turn on error reporting in your code to see these issues:

  // For mysqli
  mysqli_report(MYSQLI_REPORT_ERROR | MYSQLI_REPORT_STRICT);
  // For PDO
  $pdo->setAttribute(PDO::ATTR_ERRMODE, PDO::ERRMODE_EXCEPTION);
  

3. Fix Session Persistence Issues #

Since you're auto-logging users after registration, make sure the session is properly initialized and carrying over to the update page:

• Start sessions on every page: Every script that handles user data (including the update page) needs session_start() at the very top—before any HTML output. If you skip this, the session data won't be available.
• Avoid output before redirects: When redirecting from registration to login, make sure there's no whitespace or HTML output before header("Location: ..."). Output can break session saving, leading to missing user IDs in the update flow.

4. Check for Transaction or Commit Errors #

If you're using database transactions during registration, ensure the transaction is properly committed before the login/redirect. If the registration data is stuck in an uncommitted transaction, the update script won't see the row to modify. For example:

// PDO example: Make sure you commit after inserting
$pdo->beginTransaction();
// Insert user/shop data
$pdo->commit(); // Don't skip this!

Start with the first step (verifying your WHERE clause and session ID)—that's where 90% of these issues live. Once you confirm the target row is correct, the rest of the checks will narrow down the problem quickly.

内容的提问来源于stack exchange，提问作者ESuth