in reply to Super Search sees '//' everywhere?

I wonder if it would be worthwhile to have a checkbox to search for nodes "as rendered" rather than "as entered". I might even suggest making that the default, but that might be surprising to someone used to the old behavior.

That would require infrastructure to cache "as rendered" versions of nodes in the database so that they can be searched for. And you'd still probably very often find "//" as that is extremely common in HTML.

Read some of the previous discussions of super search to better understand the rather tight and unusual constraints it has.

- tye        

  • Comment on Re: Super Search sees '//' everywhere? (consntraints)

Replies are listed 'Best First'.
Re^2: Super Search sees '//' everywhere? (consntraints)
by Argel (Prior) on May 13, 2008 at 19:17 UTC
    Hmm. But how often does "://" come up in Perl code? Would it be possible to have Super Search exlude "://" results by default when someone searches for "//"?

      Not unless you come up with the SQL to do that (I'm pretty sure it isn't possible). Note that using regexes (RLIKE) is not an option due to their severe performance penalty (as noted in previous discussions).

      - tye        

        Has any thought been given to searching only code blocks (or excluding code blocks)? That would at least help. I guess the other option would be to replace [*://] blocks with some different sequence internally. Of course those are about as likely to happen as me committing seppuku with my cheap, dull wakizashi or tanto for even mentioning them! =:-)

        So... title only searches for the win! :-)