Master #bug9460

Hi Martin,

I have done this. I also added test file for testing TicketSearch() by CustomerIDRaw.
I added only parameter CustomerIDRaw, not CustomerLoginRaw. When I tested TicketSearch with CustomerUserLogin I did not have problem with this one. I believe this fix will be enough. 
What do you think about this?

If you think it is necessary, I will be able also to add CustomerLoginRaw.

Regards
Zoran

I have tested it, and with this line of code there is following SQL :
    WHERE 1=1 AND sq.group_id IN (1, 2, 3) AND ( st.customer_id= 'voda + vatra')
and without we have:
   WHERE 1=1 AND sq.group_id IN (1, 2, 3) AND (((st.customer_id = 'voda') AND (st.customer_id = 'vatra') )) AND ( st.customer_id= 'voda + vatra')

I believe that this line is necessary. Somewhere in Ticket Search there is %GetParam with CustomerID, and if I add CustomerIDRaw result is wrong, actually we have empty search result. But I think I should not remove in that case CustomerID from %GetParam because it can be affected on other part of code. 
For example such case is in AgentTicketSearch.pm lines: 222 and 578.
I agree we could change logic for TicketSearc generally, I'm not sure how it will be necessary in this moment. This is only my opinion about it.