We've got enough in "everything", at least, to want to search for specific queries.

E.g. I know I had some 'queries' that just PRINTed stuff, with no result sets, that would have been useful to test given your comment here. (Of course it would have been faster to type in new PRINT queries, but that wouldn't have necessarily tested the cached queries.)

It would to be useful to have inquery: and incomment: qualifiers.

I understand most queries for many SQL keywords would produce lots of results, but if the search results were displayed in a manner very similar to the current browse lists they would still be manageable and useful, especially if the results could be ordered by date as well as some of the other orderings already available for browsing.

If I could think of a good syntax to mean any order^, I'd suggest the default search means in the order given.
I.e. searching for select from where could be implemented as like '%select%from%where%' (except it should probably consider word boundaries).

^ Perhaps ( ) could be used to signify any order, so ( world hello ) will match PRINT 'Hello, world'

  • can you expand this a bit to explain how you think this should work? Search is really hard cause there is massive overlap – waffles Jun 15 '10 at 12:21
  • Now that Google search works this is not as needed. E.g. I was able to find Non-ISO WITH usage. It doesn't yet find any ISO-compatible ROLLUP or CUBE uses but sooner or later it should find mine. – Mark Hurd Jun 26 '10 at 8:03

Since 2010 a few new version of SEDE has been deployed and in the topbar there is now a search field.

search field in left topbar

The search itself is a pretty basic SQL query over the internal table QuerySet

This is how your search term is used:

builder.Where(@"  qs.Title LIKE @search 
               OR qs.[Description] LIKE @search", 
        new { search = '%' + searchCriteria.SearchTerm + '%' });

Notice that you can only search in the query Title or query Description. The SQL itself is not searchable. Your suggestion to implement it as a LIKE is followed so using % or _ or even [A-Z] in the search term behave the same as if you use those patterns in a normal TSQL LIKE statement.

Additionally there is the isfeatured:1 search option which will limit the results to only queries that are marked as featured. It seems a bit wonky but searching for isfeatured:1 finder will return a handful results. Removing the isfeatured:1 returns way more queries.

Only SEDE admins can flip the featured bit on existing queries.

See also my answer on keywords search on SEDE might need improvement

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .