Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
One rather complicated way to get what you want (may be extended to multiple calls of statements and/or procedures) is through usage of MySQL Row-Based Binary Logs as explained here. This allows fo...
Answer
#1: Initial revision
by
Alexei
·
2020-09-17T20:13:38Z (about 4 years ago)
One rather complicated way to get what you want (may be extended to multiple calls of statements and/or procedures) is through usage of MySQL Row-Based Binary Logs as explained [here](https://www.percona.com/blog/2015/01/20/identifying-useful-information-mysql-row-based-binary-logs/).
This allows for MYSQL to generate logs with affected rows that will be output like:
[Transaction total : 10 Insert(s) : 5 Update(s) : 4 Delete(s) : 1]
Applying `ShowMeBilly`'s solution to MySQL you can accumulate rows affected by using [mysql_affected_rows()](https://dev.mysql.com/doc/c-api/8.0/en/mysql-affected-rows.html).