Skip to content
This repository has been archived by the owner on Mar 28, 2023. It is now read-only.

Judge log entries don't have a timestamp #86

Open
oldmud0 opened this issue Dec 31, 2019 · 2 comments
Open

Judge log entries don't have a timestamp #86

oldmud0 opened this issue Dec 31, 2019 · 2 comments

Comments

@oldmud0
Copy link
Member

oldmud0 commented Dec 31, 2019

First, the judge log should use the database. That's what the database is for.

Second, the entries should have some kind of relative timestamp.

Otherwise, the command is worthless and should be removed.

@SudoHaugen
Copy link

Will the database only need to hold the latest 10 entries or just save all of them to the database?

@oldmud0
Copy link
Member Author

oldmud0 commented Apr 21, 2021

Just save all of them and query the latest 10.

However, there are complains about the database being too complicated for logging. So there might be some other ticket in the future about dealing with that and hauling everything logging-related back to a flat file.

Crystalwarrior referenced this issue in Crystalwarrior/KFO-Server Feb 11, 2022
* Fix #86, #87, #88, #89

* Prevent <ALL> as a valid area name+Bump up version

* Remove staff check for debug+Disable debug
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants