Missing timestamps

[Scimmia22]

All of my timestamps are showing as [None]. I haven't pinned it down, but I would guess it has to do with the database changes introduced by Quassel 0.13

[fish-face]

This might take a while to fix as I don't have a 0.13 core to hand (PRs welcome ;)) and will need to ensure backwards compatibility.

[Scimmia22]

I'll look into the database schema changes when I have a chance, maybe it won't be too bad.

[Scimmia22]

Looks like the relevant change is here:
quassel/quassel@56f686f

Just switching to storing in milliseconds. Shouldn't be bad. Now to figure out quasselgrep. :)

[curVV]

Change line 139 in query.py:
from:

columns.append("datetime(backlog.time, 'unixepoch') as time")

to:

columns.append("datetime(backlog.time / 1000, 'unixepoch') as time")

[digitalcircuit]

Ack, I forgot to offer a heads up here when making the change. Apologies for the hassle!

Yes, dividing backlog.time by 1000 as suggested by curVV should be sufficient. However, pre-0.13 databases will then be incorrect.

Two possible options:

1. Unconditionally divide, drop support for SQLite Quassel databases older than 0.13
   • Can add a comment to this effect so folks staying on older versions know what to revert
   • Simpler
2. Parse the database schema_version to determine whether to use the old (seconds) or new (milliseconds ÷ 1000) approach
   • Works for 0.12.5 and older, and 0.13
   • More to maintain