English > Support
Slashes search bug?
buah:
Try to enter only "9/11" without quotes. That's when it is happening.
Mine error is:
--- Quote ---------------madExcept 3.0 non-commercial edition---------
conversion error from string "The Fog"
Overflow occurred during datatype conversion.
Error Code:14.
--- End quote ---
It happens only if:
1. The first typed character is digit, the second one is slash and the third one is digit again. (9/11)
2. The first typed character is digit, then spaces typed as many as you want, then typed slash, then another digit (9 /11).
3. The first typed character is digit, then spaces typed as many as you want, then typed slash, then spaces typed as many as you want, then another digit (9 / 11).
4. The first typed characters are spaces typed as many as you want, then the first digit is typed, then spaces typed as many as you want, then typed slash, then spaces typed as many as you want, then another digit ( 9 / 11).
rick.ca:
--- Quote from: nostra on April 28, 2010, 06:19:49 pm ---I can't reproduce it any more. Could you send me the bug report?
--- End quote ---
Although it's a madExcept error message, there is no bug report dialog, and bugreport.txt is empty.
--- Quote ---It happens only if...
--- End quote ---
Sorry my "#/#" was so vague. :D
I did notice it still happened when spaces were inserted, but assumed that was because spaces are ignored. Now I realize that's not the case. The search string "Flash Forward" will not find "FlashForward" or "Flash<space><space>Forward"—spaces are significant. But that's for text fields (like the default titles search I've been using). A more relevant clue might be the fact the error does not occur—and spaces are ignored—if a date field is chosen. Maybe date-handling logic is being used even though the input is not a date, and a date field has not been selected.
Navigation
[0] Message Index
[*] Previous page
Go to full version