🔍 MiloDB: Finding Old Teases

[FrozenWolf]

MiloDB 2.3.0, 2024-01-31

• Database: Updated to 2023-10-31

[FrozenWolf]

MiloDB 2.4.0, 2024-02-29

• Changed: Upgraded PyInstaller to 6.4.0
• Database: Updated to 2023-11-30

[PlayfulGuy]

MiloDB 2.4.0, 2024-02-29

• Changed: Upgraded PyInstaller to 6.4.0
• Database: Updated to 2023-11-30

Thanks for the update!

Just downloaded the binaries, but the link for the source gives a 404 error.

PG

[FrozenWolf]

MiloDB 2.4.0, 2024-02-29

• Changed: Upgraded PyInstaller to 6.4.0
• Database: Updated to 2023-11-30

Thanks for the update!

Just downloaded the binaries, but the link for the source gives a 404 error.

PG

Oops! Thanks for letting me know. I made a deploy script to automatically publish the packages but I put the src package into the bin directory by accident.
It's fixed now.

-FW

[FrozenWolf]

MiloDB 2.5.0, 2024-03-31

• Database: Updated to 2023-12-31

The 'update' command will make a reappearance at some point; I'm overhauling it at the moment to make sure it really does work properly before adding it back in.

[FrozenWolf]

MiloDB 3.0.0, 2024-04-30

• Added: 'update' command to perform self updates
• Database: Updated to 2024-01-30

The '

update

' command is back by popular demand! (well, one person asked for it once). I've rewritten quite a lot of it to make sure that it actually works on both Windows and Linux. When the next release is available, it should be just a case of running '

update

' and it'll show you the change log and ask you if you want to update. The mechanism is capable of updating combinations of the application, database, and supporting files. Similar to the other commands '

help update

' will give you some more information.

If you run the '

update

' command at the moment, it should tell you that you have the current version. If it doesn't, please let me know.

[FrozenWolf]

MiloDB 3.1.0, 2024-05-31

• Fixed: Help text of 'update' command had rogue linefeed and full stop
• Changed: 'query' command can now match against partial dates
• Changed: 'update' command re-uses remote connections
• Changed: 'update' command verifies integrity of downloaded assets
• Database: Updated to 2024-02-28

Querying against partial dates

When performing a query, you can now use shorthand forms such as:

    query date = 2023

    query date = 2023-6

    query date = 2023-06

    query date = 2023-6-8

    query date > 2023

    query date > 2023-6

etc.
I'm sure you get the idea.
Thanks to trusfrated for the suggestion a loooong time ago.

Updating

If you have version 3.0.0, you should be able to update using the '

update

' command.
Please let me know if it works or doesn't work, and which operating system you use. I'm also very interested in any feedback related to your experience of the update process. Thanks!

[Carnal1]

If you have version 3.0.0, you should be able to update using the '

update

' command.
Please let me know if it works or doesn't work, and which operating system you use. I'm also very interested in any feedback related to your experience of the update process. Thanks!

Just used the update command and seemed to work flawlessly. Windows 10, Firefox. The only comment I have is it opened & closed 3(?) command windows as it progressed and seems maybe would be good to not have them close in case of a problem or to just be able to more easily see what actions had taken place, or perhaps save the actions in a log.
I'm very much appreciative of all you do with MiloDB as I find it useful quite often.

[FrozenWolf]

If you have version 3.0.0, you should be able to update using the '

update

' command.
Please let me know if it works or doesn't work, and which operating system you use. I'm also very interested in any feedback related to your experience of the update process. Thanks!

Just used the update command and seemed to work flawlessly. Windows 10, Firefox. The only comment I have is it opened & closed 3(?) command windows as it progressed and seems maybe would be good to not have them close in case of a problem or to just be able to more easily see what actions had taken place, or perhaps save the actions in a log.
I'm very much appreciative of all you do with MiloDB as I find it useful quite often.

Great, thanks for the feedback!

Performing an update of the currently running application under Windows is a bit tricky. Most commercial applications either have a separate update application or rely on a system wide-update system system like Windows-Update. The only reliable mechanism I could find to do the update under Windows was to make a temporary copy of milodb.exe, launch that to perform the update (which opens a new console, waits for the existing application to close, then updates the files), then that will launch the new application (in another new console, which waits for the temporary application to close, then cleans up the temporary copy). I did try to keep the same console window, but had all sorts of problem due to the way that Windows applications inherit console handles.

Updating under Linux is much easier due to the ability to fork a new process to replace the existing process and keep the same console, so it looks a lot cleaner.

Your suggestion of the log file is a good one. I'll have a look at producing a log that each stage of the update can contribute to so that the whole process is logged.

[Trusfrated]

When performing a query, you can now use shorthand forms such as:

    query date = 2023

    query date = 2023-6

    query date = 2023-06

    query date = 2023-6-8

    query date > 2023

    query date > 2023-6

etc.
I'm sure you get the idea.
Thanks to trusfrated for the suggestion a loooong time ago.

Seems like a great idea, even if I don't remember submitting it!

Updating

If you have version 3.0.0, you should be able to update using the '

update

' command.
Please let me know if it works or doesn't work, and which operating system you use. I'm also very interested in any feedback related to your experience of the update process. Thanks!

The update went great! Also on Windows 10 with Firefox. Very smooth and easy, I'd say.

One thing I noticed:

Code: Select all

Loaded config from 'config.json'
Warning: Config entry '/format/html/css/colour/textTableHeaderForeground' is not recognised
Warning: Config entry '/update/cacheDirectory' is not recognised

I know there's no harm but I'm not sure why these would be generating warnings in the config. Leftover from a previous version?

Thanks again! I used it tonight to find a long lost tease I was curious to see again. Could barely remember anything about it but I narrowed it down to about 100. Then I used the Browse feature to scan through the thumbnails and viola! Found it! It's amazing how the thumbnail images stick with you.

[FrozenWolf]

When performing a query, you can now use shorthand forms such as:

    query date = 2023

    query date = 2023-6

    query date = 2023-06

    query date = 2023-6-8

    query date > 2023

    query date > 2023-6

etc.
I'm sure you get the idea.
Thanks to trusfrated for the suggestion a loooong time ago.

Seems like a great idea, even if I don't remember submitting it!

It was a couple of years ago (viewtopic.php?p=322761#p322761) where you pointed out that trying to query against the rating value was difficult due to the lack of value comparison operators '=', '>', '>=', etc. That sparked off a good discussion for the long-hand/short-hand/iso-format/regional-format date comparison (viewtopic.php?p=322999#p322999). I knew I'd get it in eventually!

Updating

If you have version 3.0.0, you should be able to update using the '

update

' command.
Please let me know if it works or doesn't work, and which operating system you use. I'm also very interested in any feedback related to your experience of the update process. Thanks!

The update went great! Also on Windows 10 with Firefox. Very smooth and easy, I'd say.

Fantastic, thanks for letting me know!

One thing I noticed:

Code: Select all

Loaded config from 'config.json'
Warning: Config entry '/format/html/css/colour/textTableHeaderForeground' is not recognised
Warning: Config entry '/update/cacheDirectory' is not recognised

I know there's no harm but I'm not sure why these would be generating warnings in the config. Leftover from a previous version?

Good point; those warnings may have been around for a while but probably largely unnoticed:

• The '

  textTableHeaderForeground

  ' config setting was superseded in version 1.15, 2023-06-30 when the option to show page references with '

  browse/browseall

  ' and '

  show/showall

  ' was added.
• The '

  cacheDirectory

  ' config setting was removed in version 3.0.0, 2024-04-30 when I rewrote the update mechanism and ditched the idea for a local asset cache.

There's a half-finished '

config

' command that could do a '

config purge

' in order to clean up the config file of redundant entries. I'll see if I can finish off the other half and include in a future release.

I do have a plan to automatically migrate config settings between versions when updating. That will add/move/remove settings as needed so there should be fewer (or hopefully zero) warnings.

Thanks again! I used it tonight to find a long lost tease I was curious to see again. Could barely remember anything about it but I narrowed it down to about 100. Then I used the Browse feature to scan through the thumbnails and viola! Found it! It's amazing how the thumbnail images stick with you.

Nice!

[FrozenWolf]

MiloDB 3.2.0, 2024-06-30

• Fixed: 'query' command operator 'not' now has higher precedence as was originally intended
• Fixed: Unit test failure on Windows due to inability to delete read-only files
• Added: 'config' command to view config entries at runtime
  The new 'config' command isn't much use at the moment. It will be extended in the future to include features such as changing entries and purging redundant entries.
• Changed: 'update' command will prompt and wait for user response if there is any error during the update
  While I'm not aware of any issues with the 'update' command at the moment, if there are any errors, you'll get a chance to see them. Previously, there was a chance that the window would show the error and then immediately close leaving you non-the-wiser. In a future version, I'll probably save a log file of the update to help with diagnostics if there are any issues.
• Database: Updated to 2024-03-30

Updating

If you have version >= 3.0.0, you can use the 'update' command.

[FrozenWolf]

MiloDB 3.3.0, 2024-07-31

• Added: 'about' command to show system info and forum links
• Added: 'config purge' subcommand to purge redundant entries from the configuration file
• Changed: Replaced pip requirements-{windows,linux}.txt with requirements-{run,build,develop}.txt
• Database: Replaced non-breaking spaces with regular spaces in tease text
• Database: Updated to 2024-04-30

Update
If you have version >= 3.0.0, you can use the 'update' command.

'config purge'

This subcommand is useful if you see messages like these when starting up which are remnants from an older version:

Code: Select all

Warning: Config entry '/format/html/css/colour/textTableHeaderForeground' is not recognised
Warning: Config entry '/update/cacheDirectory' is not recognised

pip requirements-*

Those of you (if there are any) that use the source code can install the necessary pip requirements as follows:

• requirements-run.txt

  
  If you just want to run the code with '

  run.py

  '

• requirements-build.txt

  
  If you just want to build the executable with pyinstaller manually.
  Note: This includes

  requirements-run.txt

  .
  Note: If you use the '

  tools/build-bin.*

  ' scripts, they use

  requirements-build.txt

  to acquire those packages into a virtual environment.

• requirements-develop.txt

  
  If you just want to run the tests with '

  test.py

  '
  Note: This includes

  requirements-build.txt

  .
  This comprises the full set of tools that I use for development.

non-breaking spaces

I found some teases that had non-breaking spaces in the text. These are spaces that look like spaces, but won't word wrap the following word to the next line. When querying against text content, a regular space would not match against the non-breaking space because they are two different characters.
Realistically, I doubt anyone is going to notice any difference whatsoever.

[Trusfrated]

Auto-updated and purged my config file. Worked like a dream, and no warning messages anymore.

Thanks as always, FrozenWolf!

[FrozenWolf]

Auto-updated and purged my config file. Worked like a dream, and no warning messages anymore.

Thanks as always, FrozenWolf!

Great, thanks for the feedback!