ERROR on disco import -z: no such column: m_match_method

[JOJ0]

Thanks to @prcutler for reporting and finding the root cause for this bug. There definitely seems to be a wrong column name in the releases table named m_atch_method instead of m_match_method:

Adding Brainz info for track A3 on Please (24588)
Pet Shop Boys - Opportunities (Let's Make Lots Of Money)
Release MBID: 6045cfbd-ac4f-4736-b665-4f66faec4892
Recording MBID: fc8de196-f91d-401c-8ee6-5245e7aff815
Key: Cm  |  Chords Key: Cm  |  BPM: 120.202781677
ERROR DB: no such column: m_match_method
ERROR while updating release table. Continuing anyway.
1/9248```

[JOJ0]

The issue has been fixed in the commit stated above (09d2d96). In case someone faces this error with an already existing database, these are the steps to fix in a install from git in a venv or the user's environment in a homedir:

• Change into the DiscoDOS git repo: cd discodos
• Update with git pull; python setup.py develop (or ..setup py install if you prefer that).
• Run setup, schema upgrade needs to be forced: disco setup --force. Ignore the duplicate column name warnings.
• An additional column m_match_time should have been created. To clear the wrong column, it can be deleted manually:
  • sqlite3 ~/.discodos/discobase.db < sql/db_repair_2022-06-07.sql (sqlite3 binary should be available in the discodos venv)