Hi Paul!

I would do fixing with command terminal and mysql. I know it is a "nerd" job, but no can do. In this case...

First of all I hope you have done complete backup right after you noticed the error. Doing it will allow yo u play with different rescue ways and if they fail, again start from the disaster moment.

So first a copy of everything using command terminal:

cp -a ~/.config/cqrlog ~/.config/cqrlog_safe

It is also wise to copy ~/.config/cqrlog_safe to USB stick or external HD.

You can also use file manager GUI if you set "show hidden files and folders" to ON so that you can see the ".config" folder.

After doing that open cqrlog so that database engine will start.
Then from command terminal give:
mysql --socket=/home/saku/.config/cqrlog/database/sock cqrlog001

Replace "saku" with your username and "001" with your log number in use with this faulty log.

You should get mysql (or MariaDB) prompt:

MariaDB [(none)]>

Now if you know the last qso call and date before this faulty import give this command (I use my last logged qso here):

MariaDB [cqrlog004]> select id_cqrlog_main,callsign,qsodate from cqrlog_main where callsign="DL4PU" and qsodate="2020-04-15";
+----------------+----------+------------+
| id_cqrlog_main | callsign | qsodate |
+----------------+----------+------------+
| 4 | DL4PU | 2020-04-15 |
| 7 | DL4PU | 2020-04-15 |
+----------------+----------+------------+
2 rows in set (0.001 sec)

MariaDB [cqrlog004]>

You should see now 2 entries if you have all qsos duplicated.

Look at the smaller "id_cqrlog_main". If it is the last valid qso of your log all imported qsos will have bigger "id_cqrlog_main".

First we look that there are those qsos:

MariaDB [cqrlog004]> select id_cqrlog_main,callsign,qsodate from cqrlog_main where id_cqrlog_main > 4 ;
+----------------+----------+------------+
| id_cqrlog_main | callsign | qsodate |
+----------------+----------+------------+
| 5 | OH1KH | 2019-09-30 |
| 6 | G0PNM | 2020-04-15 |
| 7 | DL4PU | 2020-04-15 |

............ a long list...............finally..........

+----------------+----------+------------+
3 rows in set (0.001 sec)

MariaDB [cqrlog004]>

So row count shows how many qsos there are with bigger "id_cqrlog_main".

Then we delete them.
REMEMBER NOW THAT THE BACKUP MUST BE IN ORDER BEFORE DOING THIS!

MariaDB [cqrlog004]> delete from cqrlog_main where id_cqrlog_main>4;
Query OK, 3 rows affected (0.001 sec)

MariaDB [cqrlog004]>

Affected row count should be same as count of bigger "id_cqrlog_main".

Then you can go to cqrlog/qso_list and update log view. You should now see your log in way it was before acciedent. Qso and DXCC count should be as was.