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
{{ message }}
This repository has been archived by the owner on Apr 17, 2018. It is now read-only.
Recently I'm seeing more errors like "ArgumentError: Field-count mismatch. Expected 6 fields, but the query yielded 0" and it roughly corresponds with the upgrade to 0.10.13.
I don't know what the valid fix would be. It doesn't seem to actually be caused by an invalid query being sent to the driver.. all of these queries are the ones generated by DataMapper.
The text was updated successfully, but these errors were encountered:
Problem is that it really doesn't give any information on how to reproduce the problem. It also seems that this change might made an existing problem more obvious. Do you have any way to reproduce it? Even a repro that just throws an exception every once in a while is fine, as long as it's something I can run somewhere to try.
In general, connections should be shared across threads since that causes thread safety issues. Normally if you use the pooling properly that shouldn't happen. So it could be something that causes cross thread connection sharing. Question then would be what and how.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Recently I'm seeing more errors like "ArgumentError: Field-count mismatch. Expected 6 fields, but the query yielded 0" and it roughly corresponds with the upgrade to 0.10.13.
I think the change made in b7ba9a8 causes an invalid number of fields to be returned and for the error in https://github.com/datamapper/do/blob/master/do_mysql/ext/do_mysql/do_mysql.c#L528 to be raised.
I don't know what the valid fix would be. It doesn't seem to actually be caused by an invalid query being sent to the driver.. all of these queries are the ones generated by DataMapper.
The text was updated successfully, but these errors were encountered: