Open dkubb opened 11 years ago
@dbussink I was wondering what you thought about this?
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.
@dbussink I will see if I can work up a repro for this.
I remember this seeing before regularly (when I was still using mysql) and its seemed to be a currency problem. maybe that helps.
On Fri, Oct 11, 2013 at 5:47 PM, Dan Kubb notifications@github.com wrote:
@dbussink https://github.com/dbussink I will see if I can work up a repro for this.
— Reply to this email directly or view it on GitHubhttps://github.com/datamapper/do/issues/58#issuecomment-26152384 .
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.
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 https://github.com/datamapper/do/commit/b7ba9a842cc785230956fa9c4c235b4b030007db 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.