Author Topic: Slashes search bug?  (Read 11808 times)

0 Members and 1 Guest are viewing this topic.

buah

  • Guest
Slashes search bug?
« on: April 27, 2010, 12:33:00 am »
Try to search "Fahrenheit 9/11" without quotes? PVD crashes in my case

Offline rick.ca

  • Global Moderator
  • *****
  • Posts: 3241
  • "I'm willing to shoot you!"
    • View Profile
Re: Slashes search bug?
« Reply #1 on: April 27, 2010, 12:52:03 am »
I thought it might be a noble attempt to save you from Michael Moore's bullshit, but is seems to be a bug. I've sent a bug report.

Offline nostra

  • Administrator
  • *****
  • Posts: 2852
    • View Profile
    • Personal Video Database
Re: Slashes search bug?
« Reply #2 on: April 27, 2010, 12:59:18 am »
Thx for reporting this, will be fixed asap

Quote
I thought it might be a noble attempt to save you from Michael Moore's bullshit

Maybe I have done this unconsciously ::)

Gentlemen, you can’t fight in here! This is the War Room!

buah

  • Guest
Re: Slashes search bug?
« Reply #3 on: April 27, 2010, 01:15:06 am »
I thought it might be a noble attempt to save you from Michael Moore's bullshit

Wow! I wouldn't expect this from a Canadian, since he praises Canada in every movie? I'd like to hear something about that in a proper topic, sincerely...

Offline rick.ca

  • Global Moderator
  • *****
  • Posts: 3241
  • "I'm willing to shoot you!"
    • View Profile
Re: Slashes search bug?
« Reply #4 on: April 27, 2010, 05:04:16 am »
I've done politics and religion. Now I rant about software. We'll see. Occasionally I regress. ;)

Offline rick.ca

  • Global Moderator
  • *****
  • Posts: 3241
  • "I'm willing to shoot you!"
    • View Profile
Re: Slashes search bug?
« Reply #5 on: April 28, 2010, 02:29:30 am »
Obviously it doesn't bother me, but a search for "9/11" in version 0.9.9.21 still produces an error...

Code: [Select]
conversion error from string "300"
can't format message 13:587 -- message file C:\Program Files (x86)\firebird.msg not found
Error Code: 14.

It seems to happen just with any search string of the form "#/#"—or starting with that, if in search-as-you-type mode.

mgpw4me@yahoo.com

  • Guest
Re: Slashes search bug?
« Reply #6 on: April 28, 2010, 02:45:10 am »
Works fine in PEOPLE view...



[attachment deleted by admin]

Offline rick.ca

  • Global Moderator
  • *****
  • Posts: 3241
  • "I'm willing to shoot you!"
    • View Profile
Re: Slashes search bug?
« Reply #7 on: April 28, 2010, 05:55:13 am »
That's not in the form "#/#". If it were, it would cause the same error.

mgpw4me@yahoo.com

  • Guest
Re: Slashes search bug?
« Reply #8 on: April 28, 2010, 01:34:34 pm »
And yet it works where 9/11 doesn't in movie view.  Weird.

Ahh, now I see.  No need to hit ME with a herring.
« Last Edit: April 28, 2010, 01:37:38 pm by mgpw4me@yahoo.com »

Offline nostra

  • Administrator
  • *****
  • Posts: 2852
    • View Profile
    • Personal Video Database
Re: Slashes search bug?
« Reply #9 on: April 28, 2010, 06:19:49 pm »
Obviously it doesn't bother me, but a search for "9/11" in version 0.9.9.21 still produces an error...

Code: [Select]
conversion error from string "300"
can't format message 13:587 -- message file C:\Program Files (x86)\firebird.msg not found
Error Code: 14.

It seems to happen just with any search string of the form "#/#"—or starting with that, if in search-as-you-type mode.

I can't reproduce it any more. Could you send me the bug report?
Gentlemen, you can’t fight in here! This is the War Room!

buah

  • Guest
Re: Slashes search bug?
« Reply #10 on: April 28, 2010, 08:05:31 pm »
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.

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).

Offline rick.ca

  • Global Moderator
  • *****
  • Posts: 3241
  • "I'm willing to shoot you!"
    • View Profile
Re: Slashes search bug?
« Reply #11 on: April 28, 2010, 09:04:51 pm »
I can't reproduce it any more. Could you send me the bug report?

Although it's a madExcept error message, there is no bug report dialog, and bugreport.txt is empty.

Quote
It happens only if...

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.