Bug #103312 | MysqlHelper.executenonquery dont return affected rows correctly | ||
---|---|---|---|
Submitted: | 13 Apr 2021 21:50 | Modified: | 13 Jan 2022 17:24 |
Reporter: | mohamed atef | Email Updates: | |
Status: | Won't fix | Impact on me: | |
Category: | Connector / NET | Severity: | S3 (Non-critical) |
Version: | 8.0.23 | OS: | Windows |
Assigned to: | CPU Architecture: | Any | |
Tags: | mysqlhelper.executenonquery |
[13 Apr 2021 21:50]
mohamed atef
[14 Apr 2021 13:12]
mohamed atef
MySqlCommand.ExecuteNonQuery() Also return Invalid Affected Rows
[2 Jun 2021 7:04]
MySQL Verification Team
Hello mohamed atef, Thank you for the bug report. Verified as described. Regards, Ashwini Patil
[13 Jan 2022 17:24]
Daniel Valdez
Posted by developer: This is an actual expected behavior due to "UseAffectedRows" (default false) connection option in C/NET. If this option is set to true, then the server flag "CLIENT_FOUND_ROWS" will be set and C/NET will return the expected value as in mysql client. You can read more about this in here: https://dev.mysql.com/doc/connector-net/en/connector-net-8-0-connection-options.html https://dev.mysql.com/doc/refman/8.0/en/insert-on-duplicate.html
[13 Jan 2022 17:26]
Daniel Valdez
Posted by developer: *If this option is set to true, then the server flag "CLIENT_FOUND_ROWS" will NOT be set and C/NET will return the expected value as in mysql client.