Before inserting one or more QSO records with executemany, PyQSO currently assumes that the next row ID to be used will be max(rowid)+1. This is not always the case. Until the logbook is reloaded/refreshed, the incorrect row IDs are used which can cause problems when e.g. removing duplicate records.
ctjacobs
commented
7 years ago
Before inserting one or more QSO records with
executemany, PyQSO currently assumes that the next row ID to be used will be max(rowid)+1. This is not always the case. Until the logbook is reloaded/refreshed, the incorrect row IDs are used which can cause problems when e.g. removing duplicate records.