Bug #4295 | query 'LIKE' problem | ||
---|---|---|---|
Submitted: | 26 Jun 2004 5:39 | Modified: | 30 Jun 2004 13:14 |
Reporter: | melvin madarak | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Query Browser | Severity: | S3 (Non-critical) |
Version: | 1.0.1-alpha-win | OS: | Windows (winxp-home-editon) |
Assigned to: | Michael G. Zinner | CPU Architecture: | Any |
[26 Jun 2004 5:39]
melvin madarak
[28 Jun 2004 14:18]
Michael G. Zinner
Thanks for reporting. Could you state which MySQL server you are connecting to? Can you do selects without "like"? Could you select the table in the Schemata tree and select "Edit Table" from the Popupmenu (right mousebutton). Then please check the Charset/Collation on the "Table Options" tabsheet. Try to set it to UTF8 and hit "Apply Changes".
[30 Jun 2004 13:14]
Michael G. Zinner
The problem was caused by executing SET NAMES utf8 in the common gui library. Therefore SELECT * FROM phpbb_forums p WHERE forum_name='News' produces an "Illegal mix of collations (latin1_swedish_ci,IMPLICIT) and (utf8_general_ci,COERCIBLE) for operation '='" error but SELECT * FROM phpbb_forums p WHERE cast(forum_name AS CHAR CHARACTER SET utf8)='News' does work. To avoid unnecessary casts we now use SET CHARACTER SET utf8. This should solve the problem in all cases where there has not been a specific character set defined for a table/column. The fix will be in the next release.