3 replies to this topic

[BASHERS33]

1. Is LIKE acceptable for fields which are varchar? I'm hoping that for those fields it's not considered too bad to have to use it.

2. Does it matter what order thigns are in for the "WHERE" clause? If I put WHERE id='{$id}' and something LIKE '%something%'

would it be faster by having like on the right side or does it still not omit rows based upon the first one first anyway?

Yeah I have little knowledge of basics. lol

Also I am guessing I probably should add an index that would combine both of those fields maybe?

[BASHERS33]

ok, thanks. I had just talked to my mom also who used to eb a programmer and DBA and she said also that she saw LLIKE used often and didn't see a problem.

The reason I was wondering is because a programmer for Invision had mentioned how bad it would be if they had to run the queries using MATCH AGAINST on each page of search results. So I figured it may be that things such as LIKE or MATCH AGAINST are slow or resource intensive.

I also thought someone told me that LIKE is not used with all database drivers, but if it is used with what my mom used (DB2) and what I sue (MySQL) I am wondering if it is rerally widely used. Maybe MATCH AGAINST is the one which is only in mysql?

The way I always understood it was that match against was used for text fields and like was used for small fields.

[Orjan]

I can Believe that match against would eat more power, as it normally searches through more fields. I still see no reason to why not use them when you need to.

although, I think like would be easier on the computer, as it only matches to a string instead of several fields.