Wrong QSO number

[lpaxi765]

Hi,
I found a small bug. I activated the QSO number column and after deleting a QSO I had entered by mistake, I noticed that there is no option to renumber the QSOs. In fact, the Count on the right shows me 7270 QSOs, but the QSO number column displays 7271.

Thanks

[foldynl]

It is not a bug. QSO N is only an internal column which is uniquely numbered depending on the insertion and subsequent possible deletion of QSOs. It has nothing to do with the number of QSO.

[lpaxi765]

Sorry but I don't see the usefulness for the purposes of a station log...I could enter a QSO for testing or by mistake and delete it immediately afterwards, and the counter would continue, losing its actual numerical sequence. That would create some confusion.
And what would happen if I entered a QSO among existing ones?

[aa5sh]

That column is not a counter but an identifier. It needs to be unique and not changed. So it just goes up by one any time a qso is added.

…

On Sun, Jun 7, 2026 at 9:43 AM Lou ***@***.***> wrote: Sorry but I don't see the usefulness for the purposes of a station log...I could enter a QSO for testing or by mistake and delete it immediately afterwards, and the counter would continue, losing its actual numerical sequence. That would create some confusion. And what would happen if I entered a QSO among existing ones? — Reply to this email directly, view it on GitHub <#1061?email_source=notifications&email_token=AUEEMXXBINLRPZIT65LMVSD46V5RXA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZSGEYDENJSUZZGKYLTN5XKU43VMJZWG4TJMJSWJJLFOZSW45FMMZXW65DFOJPWG3DJMNVQ#discussioncomment-17210252>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUEEMXUIKQVDC2XYDBCJ52D46V5RXAVCNFSM6AAAAACZ5FHPF6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTOMRRGAZDKMQ> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/AUEEMXXXCCXJVNTGBHJYYD346V5RXA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZSGEYDENJSUZZGKYLTN5XKU43VMJZWG4TJMJSWJJLFOZSW45FKMZXW65DFOJPWS33T> and Android <https://github.com/notifications/mobile/android/AUEEMXRFDDSCGEEUNEATR2346V5RXA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZSGEYDENJSUZZGKYLTN5XKU43VMJZWG4TJMJSWJJLFOZSW45FOMZXW65DFOJPWC3TEOJXWSZA>. Download it today! You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[foldynl]

To avoid confusion, you can hide this column via the context menu.

[lpaxi765]

In fact, since it is a unique identifier for the SQLite scheme, I think it could lead to some misunderstandings... in many logs, the QSO number is a progressive number that indicates the number of the QSO, where the log can be renumbered when deleting or adding QSOs or printing a paper log. However, I disabled the column display. I added a QSO (an operator sent me an EQSL when he operated as a special station). The QSO identifier increased by one, as it should in the scheme, but by playing with the date reordering, it is in the correct position.