Test case: see attachment 52678 [details] of bug 42120.
1) Add a record with fname='A*' and lname left blank (or any arbitrary value).
2) Position form on this record.
3) Click on AutoFilter button (Filters the records, based on the content of the currently selected field)
Result is two records, namely "Alex Thurgood" and "A*". "Alex Thurgood" should not be in the results, since the fname is not "A*", but is "Alex".
The problem is that the generated filter is "fname LIKE 'A*'" instead of "fname = 'A*'". The "A*" in the fname field in the newly inserted record is a *value* and should not silently be treated as a *pattern*.
Note that when doing AutoFilter on lname, the generated filter is "IS EMPTY" (a synonym for "IS NULL"), not "LIKE NULL" or "LIKE ''". That is good.
Created attachment 60151 [details]
testcase with "A*" already added.
Thanks for bugreport
May be in navigator should be some check field "use patterns"? When checked, should added LIKE ' ' around.
(In reply to comment #2)
> Thanks for bugreport
> May be in navigator should be some check field "use patterns"? When checked,
> should added LIKE ' ' around.
IMO, for AutoFilter, this does not make any sense. For "filter by form", it could possibly maybe make sense, but then this comment belongs to bug 42120, not here.
Sorry. Indeed for bug 42120. May be we should change it to Functionality request?
Please: have a look on this bugreport. What is your opinion?
Lionel Elie Mamane committed a patch related to this issue.
It has been pushed to "master":
fdo#48807 autofilter should not use LIKE operator
We decided not to backport this to 3.6.x, as it is a behaviour change.
Thanks for fixing this bug