Will be fixed a future releases 7.5 and 7.6
Gert
-Ursprüngliche Nachricht-
Von: Ryan Warnick [mailto:[EMAIL PROTECTED]
Gesendet: Montag, 14. März 2005 19:53
An: maxdb@lists.mysql.com
Betreff: AW: Incorrect Query Result
Gert,
Thanks for the reply. Will this be fixed in a
2005 02:28
An: [EMAIL PROTECTED]
Betreff: AW: Incorrect Query Result
Here is a simple test case that reproduces the problem. This returns
all rows in the T1 table, when it should only return one. If you change
the LIKE expression to only have a trailing wildcard, then it returns
the correct
We are able to reproduce this join problem with LIKE predicate.
Gert
-Ursprüngliche Nachricht-
Von: Ryan Warnick [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 4. März 2005 02:28
An: maxdb@lists.mysql.com
Betreff: AW: Incorrect Query Result
Here is a simple test case that reproduces the
Here is a simple test case that reproduces the problem. This returns
all rows in the T1 table, when it should only return one. If you change
the LIKE expression to only have a trailing wildcard, then it returns
the correct result. The index on the field (F4) that the LIKE
expression is applied t
Please provide a simple test case with data.
Gert
-Ursprüngliche Nachricht-
Von: Ryan Warnick [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 2. März 2005 22:16
An: maxdb@lists.mysql.com
Betreff: Incorrect Query Result
There seems to be a problem with using LIKE expressions with a leadi
