Bug #25651 | SELECT does not work properly when WHERE contains UTF-8 characters | ||
---|---|---|---|
Submitted: | 16 Jan 2007 14:58 | Modified: | 23 Jan 2007 15:38 |
Reporter: | Tomislav Ivancic | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / NET | Severity: | S2 (Serious) |
Version: | 5.0.3 | OS: | Windows (windows xp sp2) |
Assigned to: | CPU Architecture: | Any | |
Tags: | characterset, Connector/Net |
[16 Jan 2007 14:58]
Tomislav Ivancic
[16 Jan 2007 22:13]
Reggie Burnett
Tomislav, Are you using pooling? If so, that can be it because we recently fixed a problem where connections retrieved from the pool were not getting their encoding set back up properly in some cases. Try turning pooling off and see if that fixes it. The fix that I mentioned will be in 5.0.4 Reggie
[16 Jan 2007 23:47]
Tomislav Ivancic
I added Pooling=false to my connection string (I think that is how I should turn the pooling off). That did not solve the problem. I still get the same result. The same code works fine with Connector/Net 1.0.7 and 1.0.8 (RC) with pooling on and off. Tomislav Ivancic
[17 Jan 2007 22:16]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/18297
[17 Jan 2007 22:25]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/18298
[17 Jan 2007 22:27]
Reggie Burnett
fixed in 5.0.4 and 1.0.9
[23 Jan 2007 15:38]
MC Brown
A note has been added to the 1.0.9 and 5.0.4 changelogs.