TD Helper 2 v2.0.5.2 now available from https://github.com/MarkAusten/TDHelp.../v2.0.5.2-Beta. This adds more changes to the EDDBlink options logic from eyeonus.
I am having problems with this release - details raised on github.
I still think that prune score & prune hops should be at the bottom with Age at the top, I've never used prune anything, but frequently used the rest. I guess it's where you think the important fields are more prominent - to my mind that's the top, but that may be biased by wanting to be logical, rather than ergonomic.
Have a good weekend.
TD Helper 2 v2.0.5.3 now available from https://github.com/MarkAusten/TDHelp.../v2.0.5.3-Beta. This fixes the commander update problem (I hope). This will be the last updated for a few days as I'm away until Monday.
Have a good weekend.
Have a good Bosworth. I have a shilling on Henry Tudor to win. Feeling pretty confident.
@eyeonus - I'm looking at the layout of TDH2 (again), just how narrow would you like the form to be in an ideal world?
I don't know what you are doing with your links, Mark, but you are posting them as
https://github.com/MarkAusten/TDHelp.../v2.0.5.6-Beta
Rather than
https://github.com/MarkAusten/TDHelper/releases/tag/v2.0.5.6-Beta
(click them, you'll see the difference)
Version v2.0.5.8-Beta is available from https://github.com/MarkAusten/TDHelper/releases/tag/v2.0.5.8-Beta.
This does not fix issue #30 as I cannot reproduce the error despite many attempts.
In the context of the DB update dialogue, what does "analyze" do?
It analyses the data in the database and saves a whole heap of statistics with the intent of making the query plan generation much faster. Or so I understand from the SQLite documentation. It certainly seems to help when the queries start getting very slow but it is a last resort as it take a long time to execute.
The occasional vacuum would also not go amis as the TD database can get quite fragmented.
I'm sorely tempted to remove the analyse option and add something to the documentation to explain how to run these two commands from the command line.
Maybe. I have a regular vacuum running on the server end and rarely takes more than a couple of minutes, however I did run a manual vacuum on my pc local db and got bored and left it running overnight. That said, after having run the vacuum once on my PC the next time it was double quick, so YMMV.
I don't think removing it from TDH is the correct approach. The whole point of TDH is to remove the burden of dealing with command line, for those not keyboard monkeys like me. Perhaps some more detail on the dialogue about what exactly it's going to do and some kind of warning about potential long time running.
Additionally, I don't know how you are connecting to the DB for admin tasks, but I'm presuming NOT via tradedb.py - this is good, as I wouldn't want to initiate a long running procedure with the PRAGMA options in there.