What are the potential pitfalls of using mysqli_affected_rows in PHP?

Using mysqli_affected_rows in PHP can lead to potential pitfalls because it returns the number of rows affected by the last INSERT, UPDATE, REPLACE, or DELETE query, but it may not work as expected with SELECT queries or in certain scenarios like when using ON DUPLICATE KEY UPDATE. To avoid this issue, it is recommended to use a different approach to handle the affected rows count, such as storing the count before executing another query or using a different method to retrieve the desired information. 

// Store the affected rows count before executing another query
$affected_rows = mysqli_affected_rows($connection);

// Execute another query here

// Use the stored $affected_rows value as needed
echo "Affected rows: " . $affected_rows;

Keywords

mysqli_affected_rows PHP database error handling SQL injection

Related Questions