Hi,
We got some negative reports about putting this operator first in the list. Concerns are about performance (wildcard being slower, and in case of monster tables, slower meant > 45 min.).
Before those reports, I was finding that putting LIKE '%...%' first was quite useful, as I almost always put the % manually for any search I do.
I suggest for the next -rc to put back LIKE in the first position, followed by LIKE %...%.
We could also move the list of operators from tbl_select.php to config, but this would probably be too much.
Comments?
Marc
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi Marc,
Marc Delisle wrote:
We got some negative reports about putting this operator first in the list. Concerns are about performance (wildcard being slower, and in case of monster tables, slower meant > 45 min.).
Did those guys have a fulltext index on that field? I'd bet they didn't... MySQL is faster than this, even on large tables.
Before those reports, I was finding that putting LIKE '%...%' first was quite useful, as I almost always put the % manually for any search I do.
Personally, I like placing wildcards inside my search phrase myself. That's why I never missed that feature... :-)
I suggest for the next -rc to put back LIKE in the first position, followed by LIKE %...%.
Fine for me.
We could also move the list of operators from tbl_select.php to
config,
but this would probably be too much.
Yes, this is an overkill, imho.
Regards,
- --
Alexander M. Turek rabus@users.sourceforge.net
_ __ __ _ _ _ _ __ | |__ _ __ | / |_ _ / \ __| |_ __ ___ (_)_ __ | '_ | '_ | '_ | |/| | | | | / _ \ / _` | '_ ` _ | | '_ \ | |_) | | | | |_) | | | | |_| |/ ___ \ (_| | | | | | | | | | | | .__/|_| |_| .__/|_| |_|__, /_/ ___,_|_| |_| |_|_|_| |_| |_| |_| |___/ http://www.phpmyadmin.net
Have a look at a more detailed explanation: https://sourceforge.net/tracker/index.php?func=detail&aid=1008507&gr...
Marc Delisle wrote:
Hi,
We got some negative reports about putting this operator first in the list. Concerns are about performance (wildcard being slower, and in case of monster tables, slower meant > 45 min.).
Before those reports, I was finding that putting LIKE '%...%' first was quite useful, as I almost always put the % manually for any search I do.
I suggest for the next -rc to put back LIKE in the first position, followed by LIKE %...%.
We could also move the list of operators from tbl_select.php to config, but this would probably be too much.
Comments?
Marc