| Bug #20406 | NDB query with OR and two likes | ||
|---|---|---|---|
| Submitted: | 12 Jun 2006 18:33 | Modified: | 18 Jun 2006 21:52 |
| Reporter: | Monty Taylor | Email Updates: | |
| Status: | Duplicate | Impact on me: | |
| Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S2 (Serious) |
| Version: | 5.0.21 | OS: | Linux (Linux x86_64) |
| Assigned to: | Assigned Account | CPU Architecture: | Any |
[12 Jun 2006 19:25]
Hartmut Holzgraefe
This may be charset related, i was not able to reproduce it on Linux x86 (32bit) with default latin1_swedish_ci charset settings.
[12 Jun 2006 19:44]
Monty Taylor
How could I test that? (What would the problem be?) Should I try changing the charset to something else and run the same query again? Currently it is set to latin1.
[13 Jun 2006 21:34]
Monty Taylor
I upgraded to 5.0.22 to see if the bugfix for #17421 would fix this. It did not.
[13 Jun 2006 22:39]
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/7587
[18 Jun 2006 21:52]
Pekka Nousiainen
duplicate of bug#17421 tested in "pb" on similar platforms the fix appears in 5.0.23 (not 5.0.22 which skipped patches)
Description: I have a query that is an OR condition on two like questions that returns no results when it should. I doulbe-checked with #support and they seemed to think it was probably a bug as well. How to repeat: create table testor ( fname varchar(255), lname varchar(255) ) engine=ndbcluster; insert into testor ("Young","Foo"); SELECT fname, lname FROM testor WHERE (fname like 'Y%') or (lname like 'F%'); and get an empty set. If I change to an AND, it works. If I remove one condition, it works. If I change it to equality, it works.