solidgrue

Starship Enterprise launcher!

My next mower will probably be a lawn service

San Jacincto was a different battle wherein Mexico got their collective ass kicked in there. The Alamo was a rallying cry.

Alamo itself was a rout for the Texians [sic]. There's no side-stepping that. It goes as it goes.

I didn't so much forget it as I did assume Texans were just playing the martyr for getting their collective asses kicked in. Again.

You know... Like Dallas Cowboys fans?

No worries, the other poster was just wasn't being helpful. And/or doesn't understand statistics & databases, but I don't care to speculate on that or to waste more of my time on them.

The setting above maxes out at 24h in stock builds, but can be extended beyond that if you are willing to recompile the FTL database with different parameters to allow for a deeper look back window for your query log. Even at that point, a second database setting farther down that page sets the max age of all query logs to 1y, so at best you'd get a running tally of up to a year. This would probably at the expense of performance for dashboard page loads since the number is probably computed at page load. The live DB call is intended for relatively short windows vs database lifetime.

If you want an all-time count, you'll have to track it off box because FTL doesn't provide an all-time metric, or deep enough data persistence. I was just offering up a methodology that could be an interesting and beneficial project for others with similar needs.

Hey, this was fun. See you around.

If you're wrong then I don't wanna be right.