Bug #3843
Regex search is too strict, needs work. Elog bombs on incorrect regex syntax.
Start date:
05/09/2013
Due date:
% Done:
0%
Estimated time:
History
#1 Updated by Kyle Hazelwood over 7 years ago
- Category set to Database
- Status changed from New to Assigned
- Assignee set to Kyle Hazelwood
- Priority changed from Normal to High
I'm adding a vetoableChangeListener to the elogBean that will check the regex at time of change.
#2 Updated by Kyle Hazelwood over 7 years ago
For the time being I've switched the searching to use * instead of tsvector and tsquery. I need to first create a way to sanitize user supplied tsquery syntax. Second, I need to add a tsvector column to my tables and index based on those fields. The second is merely to speed up lexeme searching so that to_tsvector does not need to be done every search. Third, create different client side fields for searching (String>LIKE, Lexemes>tsquery, Regex>*).
#3 Updated by Kyle Hazelwood over 7 years ago
- Status changed from Assigned to Closed