AUR web interface

Tasklist

FS#10301 - Repository Search feature should support regular expressions.

Attached to Project: AUR web interface
Opened by Dennis Craven (dcraven) - Sunday, 27 April 2008, 23:01 GMT
Last edited by Lukas Fleischer (lfleischer) - Thursday, 17 February 2011, 18:10 GMT
Task Type Feature Request
Category Backend
Status Closed
Assigned To Lukas Fleischer (lfleischer)
Architecture All
Severity Low
Priority Normal
Reported Version 1.5.1
Due in Version 1.8.0
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Being able to enter regex patterns into the package search field, and having them interpreted by the engine would be very handy and could cut down on the number of returned results.

Such a feature could require checking a checkbox to enable if necessary.
   . (0 KiB)
This task depends upon

Closed by  Lukas Fleischer (lfleischer)
Thursday, 17 February 2011, 18:10 GMT
Reason for closing:  Won't implement
Additional comments about closing:  http://mailman.archlinux.org/pipermail/a ur-dev/2011-February/001420.html
Comment by Dennis Craven (dcraven) - Sunday, 27 April 2008, 23:05 GMT
I just noticed this is "Powered by Flyspray". Maybe I should submit this request upstream...?
Comment by Loui Chang (louipc) - Monday, 23 June 2008, 18:40 GMT
AUR itself is totally custom so this is the appropriate place for requests.
Flyspray is just the Bug tracker.

I'm not sure regex would be the best or easiest way to narrow search results.
Maybe AND searches would be sufficient.
Comment by Gavin Bisesi (Daenyth) - Sunday, 07 December 2008, 01:41 GMT
I'd like regex searching the most myself, so long as there's a toggle for plain text searches too.
Comment by Lukas Fleischer (lfleischer) - Tuesday, 01 February 2011, 12:03 GMT
Is this really something we need? I'm a bit concerned about security as this could be easily used to start DoS attacks on sigurd. Backtracking can take a lot of time for particular regular expressions (meaning something like 10^42 years and more). I'm not sure how MySQL's RegEx parser behaves here.

Loading...