This will force the boolean to be 'AND' and eliminate the 'OR' possiblity. You should really edit you templates and fix your search submit. It will allow you to keep 'AND' or 'OR' flexibility.
[This message has been edited by pugdog (edited April 25, 2000).]
But, I started to play with it, and got some really funny results.
I even set $bool='AND' right before the queries were sent, and it didn't work.
I'm going to have to pass this to Alex.
What 'appears' to work, isn't. I thought it was working, but my searches may have been flawed... I can't even seem to force an 'AND' search even editing DBSQL.pm.
I also have the same problem with regard to search.cgi always returning in the "OR" mode. This happens even when the boolean "AND" is included either as a user-defined, or hidden field ("bool" = "AND")on the search form.
So if you type in the search term "Art Schools" you will still get anything with "Art" or anything with "Schools", rather than just those that have both terms "Art" and "Schools" in them.
I haven't changed anything on search.cgi which has the following:
I haven't found a fix. I played with it for awhile.
Hopefully it will be fixed in the next release. I never noticed that before, which is odd.... but it did get a little frustrating once I saw it, and couldn't figure out a way around it.