Difference between revisions of "OpenDBX/C API/odbx rows affected"
(enhanced article) |
(error) |
||
| Line 14: | Line 14: | ||
= Return values = | = Return values = | ||
| − | '''odbx_rows_affected()''' returns the number of changed rows on success and zero if the database server didn't alter any rows. A value of zero can be returned due to the conditions in the WHERE clause of the statement which doesn't match any rows | + | '''odbx_rows_affected()''' returns the number of changed rows on success and zero if the database server didn't alter any rows. A value of zero can be returned due to the conditions in the WHERE clause of the statement which doesn't match any rows. |
= Errors = | = Errors = | ||
| − | This function | + | This function will also return zero if the '''result''' parameter is invalid. |
= See also = | = See also = | ||
Revision as of 21:19, 24 April 2007
#include <odbx.h>
uint64_t odbx_rows_affected(
odbx_result_t* result )
Description
Returns the number of rows that have been changed by the current statement whose result was retrieved by odbx_result(). Affected rows are only returned for DELETE, INSERT or UPDATE statements and their number depends on the database implementation. Instead returning the number of rows which are matched by the WHERE clause, MySQL does only count the rows whose values have really been changed.
The result parameter required by this function must be a valid result set returned by odbx_result() and must not have been feed to odbx_result_free() before.
Return values
odbx_rows_affected() returns the number of changed rows on success and zero if the database server didn't alter any rows. A value of zero can be returned due to the conditions in the WHERE clause of the statement which doesn't match any rows.
Errors
This function will also return zero if the result parameter is invalid.
See also
Back to Overview
