Skip to content

can patchew search be switched to not insist on exact full-word matches? #126

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
pm215 opened this issue Jun 15, 2020 · 2 comments
Open

Comments

@pm215
Copy link

pm215 commented Jun 15, 2020

It would be nice if patchew was less strict about only searching for exact word matches. For instance, you can only find this patch:
https://patchew.org/QEMU/[email protected]/
("hw/timer/a9gtimer: Clear pending interrupt, after the clear of Event flag")
if you search for "hw/timer/a9gtimer", because it does not match a search for "a9gtimer". (As a comparison, the "patches" command line tool doesn't do word-matches, so this patch can be found by searching for "a9gtimer" or even just "gtimer".)

@bonzini
Copy link
Contributor

bonzini commented Jun 15, 2020

Matching on full words gives is by design, but splitting on slashes is definitely a good idea. We use postgres full text search so I have to figure out how to configure it (or perhaps just replace non-ascii characters with spaces before indexing).

@bonzini
Copy link
Contributor

bonzini commented Feb 22, 2022

I tried doing this on next.patchew.org, but the most straightforward way in postgres seems to be to have another field with the searchable content. updating the database to create it took too much time (i halted it after a couple minutes) even if it is in theory just a few thousand rows.

I may revisit it later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants