Skip to content

Commit 3a3b8a7

Browse files
committed
Highlight SELECT queries as cause of issues with sql_affectedrows
1 parent c791595 commit 3a3b8a7

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

development/db/dbal.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -384,7 +384,7 @@ Example:
384384
$affected_rows = $db->sql_affectedrows();
385385
386386
.. warning::
387-
Be cautious when using ``sql_affectedrows()`` to determine the number of rows affected by your query.
387+
Be cautious when using ``sql_affectedrows()`` to determine the number of rows affected by your query, especially with **SELECT** queries.
388388
This function's behavior can differ depending on the used database driver and whether the query was cached.
389389

390390
Do not rely solely on ``sql_affectedrows()`` to confirm the number of impacted rows. Consider alternative approaches

0 commit comments

Comments
 (0)