<p>You are absolutely right removing it would cause problems, but I don't suggest doing that, if you look at bug 5515 you will see I suggest we use something other than and for the directive perhaps +++ and then change build query to use that.</p>
<p>People could still use ccl from the browser if they type ccl= but all other searches would be constructed by buildquery and would look like ti=the hobbit +++ au=tolkien. Which would mean ti=and simple +++ au=bob would work too. We might want to do the same with or and not.</p>
<p>Hope this makes sense, typed on my phone while taking a break from christmas shopping. Merry christmas to your family Henri Damien, and to everyone else in the Koha family :)</p>
<p>Chris </p>
<p><blockquote type="cite">On 18 Dec 2010 07:08, "LAURENT Henri-Damien" <<a href="mailto:henridamien.laurent@biblibre.com">henridamien.laurent@biblibre.com</a>> wrote:<br><br>Le 17/12/2010 18:17, Chris Cormack a écrit :<br>
<p><font color="#500050">> On 17 December 2010 23:46, LAURENT Henri-Damien<br>> <<a href="mailto:henridamien.laurent@biblibre.com">henridamien.laurent@biblibre.com</a>> wrote:<br>>> Le ...</font></p>mmm... removing and from ccl properties would break all the crossed<br>
searches...<br>
say I want Title=Stories and author=Poe and pb=Penguin<br>
Removing and from ccl.properties... would make it fail.<br>
Hope that helps.<br>
--<br>
<font color="#888888">Henri-Damien LAURENT<br>
</font></blockquote></p>