about summary refs log tree commit diff
path: root/litterbox.c (follow)
Commit message (Collapse)AuthorAge
* Don't special case user being * in queriesJune McEnroe2020-01-01
| | | | | | It's a side-effect of imports that shouldn't surface elsewhere. Would be nice to have unscoop figure out how it can eliminate using * in more places.
* Factor out hashing functionJune McEnroe2020-01-01
|
* Join with USING wherever possibleJune McEnroe2019-12-30
|
* Order results by ID in outer query in litterboxJune McEnroe2019-12-30
|
* Add limit option for litterbox's search query interfaceJune McEnroe2019-12-30
|
* Send fts5 errors in response to queriesJune McEnroe2019-12-28
|
* Don't insert self-messagesJune McEnroe2019-12-28
| | | | | Even with NOTICEs litterbox would sometimes receive its own responses, which would create duplicates in the database, essentially.
* Call tls_close and dbClose in atexitJune McEnroe2019-12-28
|
* Move querySearch code aroundJune McEnroe2019-12-27
|
* Add nick coloring to search query resultsJune McEnroe2019-12-27
|
* Reply to search queries with NOTICEJune McEnroe2019-12-27
| | | | | When connected to pounce, it's possible to receive some of its own PMs, so it should respond with what can't be commands.
* Add search query interfaceJune McEnroe2019-12-27
|
* Use bsearch to find handlerJune McEnroe2019-12-26
| | | | | | | | | The code is a bit cleaner this way I think, and performance would be better if the list of handlers ever got very long, and it was sorted anyway. However, I would prefer if there were a way to enforce the list being sorted at compile-time.
* Handle ERRORJune McEnroe2019-12-26
|
* Make sure context exists in handleReplyTopicJune McEnroe2019-12-26
|
* Inline queries, move stuff aroundJune McEnroe2019-12-25
| | | | | | No idea now why I wanted to have network bound all the time. Ended up creating a copy of the string for each statement instead of just having one like this.
* Treat topics like motdsJune McEnroe2019-12-25
| | | | | It's more like a cache of existing topics. events is still meant to record actual topic events.
* Insert MOTDs into the databaseJune McEnroe2019-12-25
|
* Insert existing topics into the databaseJune McEnroe2019-12-25
| | | | | | | Not sure how to handle the 333 reply that contains the user who set the topic and the timestamp of when it was set, since they're two separate messages that aren't really easily correlated since there's no guarantee that you're even going to get a 333 at all.
* Handle SIGINT and SIGTERMJune McEnroe2019-12-25
|
* Only send JOIN if there are channels to joinJune McEnroe2019-12-25
|
* Broadcast nick to user and host if they're unsetJune McEnroe2019-12-25
|
* Handle NAMES replyJune McEnroe2019-12-24
|
* Handle topicJune McEnroe2019-12-24
|
* Handle quitJune McEnroe2019-12-24
|
* It's The Big RefactorJune McEnroe2019-12-24
|
* Actually only use a transaction for handlers that need itJune McEnroe2019-12-23
| | | | How did I manage that?
* Take optional explicit path in dbFindJune McEnroe2019-12-23
|
* Factour out verbose, dbStep+resetJune McEnroe2019-12-23
|
* Handle NICKJune McEnroe2019-12-18
|
* Handle JOIN, PART and KICKJune McEnroe2019-12-18
|
* Rearrange SQL and IRC codeJune McEnroe2019-12-18
|
* Wrap handlers in transactionsJune McEnroe2019-12-18
|
* Rewrite litterbox statements with functionsJune McEnroe2019-12-18
|
* Insert events for PRIVMSG and NOTICEJune McEnroe2019-12-17
|
* Handle ISUPPORTJune McEnroe2019-12-17
|
* Implement -j joinJune McEnroe2019-12-17
|
* Implement basic IRC connection and message parsingJune McEnroe2019-12-17
|
* Style cleanupJune McEnroe2019-12-13
|
* Implement DB initialization and migrationJune McEnroe2019-12-02
|
* Rename header file to database.hJune McEnroe2019-12-01
|
* Implement database file searchJune McEnroe2019-12-01
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-11-23 21:10:47 +0000