Hello,

ok, it's not realy a but report but maybe a discussion, if CQRLOG has a problem with MariaDB 10.4 and how to fix it. At the moment, there are two topics with problems which are based on MariaDB 10.4

* https://www.cqrlog.com/node/2269
* https://www.cqrlog.com/node/2272

I use CQRLOG on ArchLinux (2.3.0) but not with a local stored database. I have a server in my home network which runs with MariaDB 10.4. So I have not the problem with the "mariadb-upgrade" to bring the database to the new format. But I can see different other problems.

So I am not able to import an adif file to the database (maybe a general problem with my adif files but I tried three different files and got this error and I imported them a year ago...) - CQRLOG reports complete and shows me only a view records of the adif file...:

1
2
3
4
5
insert into cqrlog_main (qsodate,time_on,time_off,callsign,freq,mode,rst_s,rst_r,name,qth,qsl_s,qsl_r,qsl_via,iota,pwr,itu,waz,loc,my_loc,remarks,county,adif,idcall,award,band,state,cont,profile,lotw_qslsdate,lotw_qsls,lotw_qslrdate,lotw_qslr,qsls_date,qslr_date,eqsl_qslsdate,eqsl_qsl_sent,eqsl_qslrdate,eqsl_qsl_rcvd, prop_mode, satellite, rxfreq) values(:qsodate,:time_on,:time_off,:callsign,:freq,:mode,:rst_s,:rst_r,:name,:qth,:qsl_s,:qsl_r,:qsl_via,:iota,:pwr,:itu,:waz,:loc,:my_loc,:remarks,:county,:adif,:idcall,:award,:band,:state,:cont,:profile,:lotw_qslsdate,:lotw_qsls,:lotw_qslrdate,:lotw_qslr,:qsls_date,:qslr_date,:eqsl_qslsdate,:eqsl_qsl_sent,:eqsl_qslrdate,:eqsl_qsl_rcvd, :prop_mode, :satellite, :rxfreq)

Import failed! TMySQL56Connection : Error executing query: Incorrect string value: '\xE1bor' for column `cqrlog002`.`cqrlog_main`.`name` at row 1
It takes about 0 minutes and 0 seconds 69 milliseconds

I can also reproduce this problem with old CQRLOG backups.

(without debuglog and without I can reproduce that)
Yesterday I edit a record (change the name), the log record was lost. That should never happen. Today every change of a record works fine.

Rebuilding the DXCC statistic with only 149 QSOs created an crash of the program.
select band,count(distinct adif) from cqrlog_main where adif <> 0 and qsl_r = 'Q' and (adif not in (2,8,19,23,25,26,28,30,39,42,44,55,57,58,59,67,68,81,85,93,101,102,113,115,119,127,128,134,139,151,154,155,164,178,183,184,186,193,193,194,196,198,200,208,210,218,220,226,228,229,231,243,244,255,258,261,264,267,268,271,307,488,493)) and ((mode<>'CW') and (mode<>'CWR') and (mode<>'SSB') and (mode<>'FM')and (mode<>'AM')) group by band

Section:frmDXCCStat
Saving window size a position (frmDXCCStat) (height|width|top|left):529|711|27|20
SELECT COUNT(*) FROM cqrlog_main

select id_cqrlog_main,qsodate,callsign,adif,qso_dxcc from cqrlog_main

select * from view_cqrlog_main_by_qsodate LIMIT 500

TApplication.HandleException Access violation
Stack trace:
$00000000009216A8
$00000000008B2EF2
$00000000008B31D5
$00000000008B250D
$00000000008AE0FA
$000000000084B210
$00000000008ADF43
$00000000008499B5
$0000000000670B56
$00000000006577B8
$000000000065BCF9
$0000000000670A8C
$0000000000431FAF
$0000000000658D8D
$000000000084CCEA
$00000000008A90DD
$000000000082DB32

That are only a view things a tried. But I cannot trust a program which does not store the data clearly. So what can we do? Back to MariaDB 10.2/.3?

73 Tobias, DF1NIF