Re: Where and Case sensitivity

[Joey JJ]

Thanks Rick,
I don't think I had fully understood utf8_unicode_ci then, I assumed that it removed the ability to store case sensitive strings.
I suppose this is why this is the Newbie section - but then I didn't test this assumption either!

If I could just expand on two points to hopefully gain some more guidance?

1. The temporary table (t_CurrentKeywords) exists because there will eventually be
millions of rows in the initial Extracted table (ExtractedWordsToMatch).
However these will be inserted ~1-2,000 per time.
So would you suggest that I perhaps Index ExtractedWordsToMatch.word prior to insert and then skip out the whole Temp table?

2. The extracted words will contain many duplicates. I was using DISTINCT to remove these, so I guess that makes the WHERE EXISTS function redundant anyway.
Would the JOIN work faster still without the distinct?
I don't want the matching to be case sensitive, so I'll use utf8_unicode_ci. I just want the text returned in the format as was set in OfficialWordList.word


Thanks again

Joey