I started a small project to work on a better search solution for quassel some time ago, if you'd like, you can contribute at https://github.com/justjanne/quassel-rest-search
(Works only with postgresql, but uses word2vec for better search results)
Why not just open the sqlite file and search in there? Could even ask for the log to be stored in an FTS table for fast FTS queries.
Is this really a problem?
I think it's nice you can do all the SQL dumping/munging stuff, given the implementation. I just don't want that in 99% of all use cases - the application doing search itself is enough normally. It's not like I use any of grep's more powerful features when I search logs, 99% of the time it's just something like "| grep foo" and I narrow it down iteratively or just pick out the result.
Honestly, technical specifics aside, this is also a matter of usability, and is something Slack gets very right: you never have to do anything for search to work well for the vast majority of use cases, even for very long histories. You just type the words you want and the results always come back, even from weeks or months before. Telling users to enable logs and then search text files is just much more activation energy. Telling them to do that after exporting their data from SQLite, even more so.
While searching for things in the immediately loaded buffer is easy (CTRL+F), searching for things said a long time ago can't be searched via the client. You either have to use command line tools to dump the sqlite db into a grepable text file or install the quasselsuche web app (last updated in 2012).
Once better long term search has been implemented in the client, quassel will become the best GUI IRC client hands down, I look forward to seeing the progress made in this area.