LPS-46692

Hey Hugo,

So since LPS-46720 was rejected by Ray, I decided to just go ahead and not worry about encoding the ">" character in the database and just address the issue at hand (which also resolves the verify process issue I emailed you about). What is happening is that the & and < characters are encoded in the database, so when we search with double quotes, & != &amp;. This fix passes in a new parameter when the characters need to be encoded so that the search works properly. I applied it to all of the cases where the CustomSQL.keywords method was used and the terms being search had the encoded characters in the database. All of the other cases were unencoded.

If you have any questions, let me know. Thanks.