You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Again mysqlclient communication looks valid, but everything looks like affected_rows cleared between query execution and mysql_affected_rows call (e.g. with mysql_next_result).
The text was updated successfully, but these errors were encountered:
It's definitely not thread-safe. You must not share a MySQL connection concurrently across threads. Using a thread pool is safe iff all uses of the connection in thread A are fully retired before the connection is made usable again by thread B.
I'm not sure I'm following the issue? Active Record provides a thread pool that is compliant to the restriction above.
Exception raised from: https://github.com/rails/rails/blob/v4.2.7/activerecord/lib/active_record/connection_adapters/mysql2_adapter.rb#L253
The issue could be related to:
#461 (comment)
With break point inside libmysqlclient18 (ubuntu 14.04 5.5.57):
b mysql_affected_rows if mysql->affected_rows > 100000
Buffer contains normal confirmation to server response and part of previous server response:
Another run with same affected_rows == -1 error under strace:
Again mysqlclient communication looks valid, but everything looks like affected_rows cleared between query execution and mysql_affected_rows call (e.g. with mysql_next_result).
The text was updated successfully, but these errors were encountered: