Store epoch to correct entry, fix uninitialized variable

[JonOfUs]

Found a bug in the migration: the UPDATE SQL query updates all entries where timestamp_epoch is 0. On my setup (sqlite) this lead to identical timestamp_epoch values in each updated entry. Selecting the entries by their id's fixes this.

Additionally, this fixes #39 by initializing $result.

[thrillfall]

Thanks for fixing this. But can you please add a test that verifies the correct value migration? Should have done it myself before, but hey 🤦

[JonOfUs]

Do you mean a unit test for developing purposes or a test inside the migration function itself?

[thrillfall]

Do you mean an unit test for developing purposes or a test inside the migration function itself?

The first please.
What would happen if the test failed when you test within the migration function? I dont get it 😄

[JonOfUs]

I probably don't have time until tomorrow, so if you have time, you could add the test too. Since we already have a test for the migration feature that only tests with one EpisodeAction (so it didn't find the bug) this change shouldn't take too long.

I just wasn't sure what kind of test you mean. Ensuring that all carried out migrations went right in running instances could be useful because now probably many timestamps are incorrect (prob. ignorable problem, because it's a constantly changing value).

[thrillfall]

I extend the test.
Lesson learned (yet again): never test with only one item. 🤦

[thrillfall]

pushed you all commit to main