+- CoreBOSBB (https://discussions.corebos.org)
+-- Forum: Development (https://discussions.corebos.org/forumdisplay.php?fid=18)
+--- Forum: coreBOS Development (https://discussions.corebos.org/forumdisplay.php?fid=4)
+---- Forum: coreBOS (https://discussions.corebos.org/forumdisplay.php?fid=5)
+---- Thread: MySQL >= 5.5.3 bug (/showthread.php?tid=224)
MySQL >= 5.5.3 bug - addady2 - 12-18-2015
Hello
One of my customer face this issue:
https://discussions.vtiger.com/index.php?p=/discussion/comment/1198220
FYI: After check coreBOS code it look like the above vtiger issue also relevance to coreBOS.
Regards
Addady
RE: MySQL >= 5.5.3 bug - joebordes - 12-20-2015
Hi,
I dedicated some time to this today and found that the solution proposed isn't exactly equivalent to the current functionality. As the global search is right now, it ignores case, in other words it is a case insensitive search, but with the change proposed it is converted into a case sensitive search so it doesn't return the same results.
I made a minor change to make the functionality equivalent but it makes the search work slower and since in the majority of installs it really isn't necessary I added a global variable so it can be activated only if needed.
https://github.com/tsolucio/corebos/commit/5fc4fd795e9b5bba0bca9b3649bf698c836f4b2a
Thank you very much for sharing :-)
RE: MySQL >= 5.5.3 bug - addady2 - 12-21-2015
Hi,
I believe to need another parameter. One that allow to use if faster without the LOWER function.
As I understand it , every Corebos using MySQL >= 5.5.3 will need you use the BINARY function, in order to search non Latin characters.
Addady
RE: MySQL >= 5.5.3 bug - joebordes - 12-21-2015
I would prefer to keep the functionality equivalent. I mean to keep both search types case insensitive, because that is the way it has always been, but if you can send me a PR I will consider it.