php and mysql

Follow-up for @kishan4u1 — since @MagicMedia's session tip got the cart working and @mulkave pointed to POST/AJAX, here is a practical, durable checkout workflow and database pattern to move the session cart into MySQL, validate it, and handle removals safely.

Decide when to persist: recommended practice is to write a real order to the DB only when checkout is confirmed (shipping + payment). Alternatively keep a draft cart table for logged-in users. Typical schema: orders (id, user_id, total, status, created_at, shipping fields), order_items (id, order_id, product_id, sku, name_snapshot, qty, unit_price, line_total). Always snapshot name/price in order_items so future product changes don’t corrupt past orders. Use InnoDB and server-side prepared statements (PDO or MySQLi). Recalculate totals on the server — never trust client-sent totals.

Example checkout transaction (PDO-style pseudocode):

$db->beginTransaction();

$sth = $db->prepare("INSERT INTO orders (user_id,total,status,created_at) VALUES (?,?,?,NOW())");
$sth->execute([$user_id, $total, 'pending']);
$order_id = $db->lastInsertId();

foreach ($cart as $item) {
  $db->prepare("INSERT INTO order_items (order_id,product_id,qty,unit_price,name) VALUES (?,?,?,?,?)")
     ->execute([$order_id,$item['id'],$item['qty'],$item['price'],$item['name']]);

  $upd = $db->prepare("UPDATE products SET stock = stock - ? WHERE id = ? AND stock >= ?");
  $upd->execute([$item['qty'],$item['id'],$item['qty']]);
  if ($upd->rowCount() == 0) { $db->rollBack(); /* handle out-of-stock */ exit; }
}

$db->commit();

Practical tips: keep the session cart as the editable source until final submit; if saving drafts, mark them with status='draft'. For stock safety use atomic UPDATE (shown) or SELECT ... FOR UPDATE inside the same transaction to avoid oversells. Use CSRF tokens, server-side validation, and sanitize inputs. For payment flows, mark payment_status after gateway callback and only finalize shipments thereafter. These steps cover passing the session cart into MySQL, concurrent-safe stock updates, and clean removal handling.