diff options
author | zlg <zlg@zlg.space> | 2023-09-22 01:02:37 -0700 |
---|---|---|
committer | zlg <zlg@zlg.space> | 2023-09-22 01:02:37 -0700 |
commit | cb4300cd23ed4af9207d23c0b437870294cb161c (patch) | |
tree | c47074f62a5aee1675523a765febd4015f3aeb5c /TODO.txt | |
parent | tests: Add long-lost test_import.json (diff) | |
download | vgstash-next.tar.gz vgstash-next.tar.bz2 vgstash-next.tar.xz vgstash-next.zip |
scripts: Add schema v1->v2 migration scriptnext
This script adds three columns to the schema, supporting the
"Purchased", "Beaten", and "Completed" note headers. They are now
converted to a UNIX timestamp and stored in a separate column so queries
made against that metadata are easier.
The library itself still needs to support all the new columns.
Diffstat (limited to '')
-rw-r--r-- | TODO.txt | 10 |
1 files changed, 1 insertions, 9 deletions
@@ -1,20 +1,12 @@ -* Get tests running in their own directory * Write CLI * in progress, using click - https://click.pocoo.org/ * Write GUI + * in progress (tkinter) * Write docs * How? Sphinx? Needs research --- -Consider adding a 'dates' table that matches games to dates for purchase, -beating, and completing. Currently implemented via RFC2822-style headers within -the 'notes' field. More research is needed to determine if the notes field or a -table is a better way to achieve this. If an addition to the database format is -deemed necessary, a restructuring may be in order. - ---- - One of the things curious about managing a game collection that doubles as a backlog is, you get games on systems that were originally on other systems. How do you classify those games? The original game is the actual content you're |