Bug #25159 Cant search for next occurance fails when case is different
Submitted: 18 Dec 2006 22:57 Modified: 10 Jan 2007 5:33
Reporter: Jared S (Silver Quality Contributor) Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Query Browser Severity:S2 (Serious)
Version:1.2.8 OS:Windows (WinXP\Vista)
Assigned to: CPU Architecture:Any
Tags: next, quer browser, search

[18 Dec 2006 22:57] Jared S
Description:
Hi.  Search for next functionality is either broken or doesn't exist in script editor.

How to repeat:
1. Load large script
2. Search for some common text like word 'table'
3. Then click search butoon again

Suggested fix:
Enable search next functionality.
[22 Dec 2006 18:04] MySQL Verification Team
Thank you for the bug report. I was unable to repeat the behavior reported.
I followed your instructions with the word 'Table'.
[23 Dec 2006 8:40] Jared S
Hi,  I have a file which when loaded triggers the search bug.  Simply load the attached file into QB.EXE and run and then search for word like 'table'.
[23 Dec 2006 9:03] Jared S
Even with the last file I just uploaded, I can not repeat the problem now, you may want to wait until I can get an even better test case.
[23 Dec 2006 9:13] Jared S
Hi.  I can now repeat the bug at my will.  With last file uploaded please search for the following text with *exact* lower casing.

'using btree'

-- finds nothing, although it should.
[23 Dec 2006 14:26] Valeriy Kravchuk
Please, describe how you can repeat it in a new comment.
[25 Dec 2006 20:33] Jared S
Hi.  Here are steps to repeat.

1. Download my uploaded sample DB file called 'Cyco20061214 1247.rar'
2. Restore this database to a server (5.0.27 ideal)
3. Start Query Browser 
4. Search for 'using btree' (has to be in lower case)

# Search doesn't find anything but there are many occurances of 'USING BTREE'
# Search will find it if you use upper case
[3 Jan 2007 22:53] Jared S
Can some one have another go a validating this bug.  Have re-supplied a new file above with new set of instructions.
[10 Jan 2007 5:33] Jared S
starting a fresh bug cause problem was poorly identified.