What steps will reproduce the problem?
1. Open a resultset
2. Do a (default) accurate search using a string as search value
What is the expected output? What do you see instead?
Every record in the resultset that contains the search value. However it
returns also records that do not contains the search value.
Using the query string to do the same search on another SQL client returns
the same results: the "bug" is related to MySQL (?) behavior. For MySQL the
query:
SELECT 0='foo'
returns 1=TRUE hence the result in Jardin is MySQL-ly correct but is not what
users expect.
Original issue reported on code.google.com by gpantane...@gmail.com on 13 May 2010 at 8:55
Original issue reported on code.google.com by
gpantane...@gmail.com
on 13 May 2010 at 8:55