This repository has been archived by the owner on Mar 28, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 51
Stop using SQLite for logging server events like IC and OOC #190
Comments
Legacy branch's logger for KFO did the job: https://github.com/Crystalwarrior/KFO-Server/blob/legacy/old2018/server/logger.py |
working on it |
Oh yeah since you discontinued tsu3 wanna help kfo server :) |
Yeah I'm changing my changes to do a PR on kfo-server. It's a slightly different codebase. I'm planning to support two different formats:
I don't think there is a substantial demand for the latter, so I might just keep that change specific to my server. |
any progress on this |
🪦 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
SQLite should only be used for handling bans, etc. Handling the area logs is only leading it to grow in size, and it's disgustingly easy to corrupt the database when trying to view the logs. It takes 30 seconds to run any given schema on especially large databases.
The solution is to bring back text logging for anything that's not benefiting from SQLite-specific features, such as bans.
also see Crystalwarrior/KFO-Server#11, same issue since KFO is a fork of tsu3. Planning to attempt some solutions on my end at some point.
The text was updated successfully, but these errors were encountered: