All the Microsoft engines perform wildcard searches based upon *. I forgot to change it back to % in one of my lines above.
The Microsoft Wildcard string expression logic is:
* Matches zero or more characters. It can be used as the first or last character in the character string. wh* finds wh, what, white, and why
? Matches any single alphabetic character. b?ll finds ball, bell, and bill
[ ] Matches any single character within the brackets. b[ae]ll finds ball and bell but not bill
! Matches any character not in the brackets. b[!ae]ll finds bill and bull but not ball or bell
- Matches any one of a range of characters. You must specify the range in ascending order
(A to Z, not Z to A
). b[a-c]d finds bad, bbd, and bcd
# Matches any single numeric character. 1#3 finds 103, 113, and 123
Facinating on the headline like conundrum. My MySQL experience is nothing more than hours really. There's me wrapped up in my own little Microsoft world
The array is probably a better way to do it than a straight implantation of keywords into a wildcard string, like with the SELECT * there is probably an overhead involved while the system generates its own SQL from it. I shall see about experimenting with the HCL's search system at some point, that's a bit clunky
(still the HCL3 RTM code from when the index was first automated
).
I'm not the worlds greatest programmer, I never will be. In fact I'm really a newbie+9 these days. Which is better than I was 12 months ago. Doesn't exactly come naturally to me, but I seem to have managed to hand write this site and all it's automation. So I guess I cannot be all that bad. It is all ASP3.
I don't know C, probably should get a book. I would like to be able to do something in the eVC++ IDE.