in reply to
So why don't you
1) do your searches before encoding
2) decode to some temporary location for the purpose of searching
3) encode your search expression with the same encoder and procedure as well
I think I know that now, thanks to Anonymous Monk. I will be using "prepared statements" in Java to load the SQL. As I understand it, then one does not have to encode text for insertion.
Aren't I on the right track then Ikegami?
I thought this link might be helpful for others: Prepared SQL statements in Java
Priority 1, Priority 2, Priority 3
Priority 1, Priority 0, Priority -1
Urgent, important, favour
Data loss, bug, enhancement
Out of scope, out of budget, out of line
Family, friends, work
Impossible, inconceivable, implemented
Results (57 votes),