Author: mail
Description:
the fix
I brought this up on the mailing list a while ago:
http://groups.google.com/group/semantic-forms/browse_thread/thread/1d92f80ac8f8d4ee/2fce47200af23513?lnk=gst#2fce47200af23513
Now I updated to version 1.7.2 from 1.6 and found that the bug is still present, so I'm trying it via the bugtracker ;)
As it is now, SF's autocompletion does only work in some cases on properties - see for yourself at the specified URL (my Wiki is currently running vanilla SF 1.7.2, without my patch): Start with entering an 'a' into the "Test autocomplete on property (remote)" field. You will get "Abcd Efgh" and "abcd efgh" in the autocompletion list. Now empty the field and start with entering an 'e', which should bring up those two again, but nothing will come up. The attached patch fixes this problem.
The problem I fixed, was, that MySQL's LOWER() [1] does not work on BINARY, VARBINARY and BLOB. But page_title is (at least in my database) of type VARBINARY. I changed the SQL queries so that all arguments to LOWER() function calls are converted to UTF8 first.
Version: unspecified
Severity: normal
URL: http://patrick-nagel.net/wiki/Special:AddData/Test_autocomplete_on_property/X
attachment sf_autocomp_case3.patch ignored as obsolete