I was moving things over to a new computer and when I imported the ADIF from my old log, I noticed the eqsl sent/received flags weren't showing up. The associated dates are there, but not the 'Y' in those columns. I even tried adding them via the SQL console but it doesn't seem to have updated. Any ideas? (This is on xubuntu 22.04.4 with a version I built from source with mariadb as the database server. There's on in the xubuntu repo but it fails to start w/mysql errors that I've not yet debugged and I recall reading the official cqrlog repo doesn't support 22.04).
Sun, 2024-03-03 18:10
#1
Can't seem to update eqsl_qsl_sent and eqsl_qsl_rcvd
HI!
Sound weird that you can not change database content via QSL console.
update cqrlog_main set eqsl_qsl_sent='Y' where eqsl_qslsdate<>''
How ever perhaps first check
select qsodate,time_on,callsign from cqrlog_main where eqsl_qsl_sent='' and eqsl_qslsdate<>''
Other way is use Qsolist/group edit if you do not care about keeping the old eqsl date. Setting Y there sets also the date as current date.
As you have compiled cqrlog (source from where) you may also like to check https://htmlpreview.github.io/?https://github.com/OH1KH/cqrlog/blob/loc_...
Corresponding source can be found from https://github.com/OH1KH/cqrlog/tree/loc_testing
--
Saku
OH1KH
Thanks, Saku.
Well this is interesting...I ran your "select" query and it returned nothing, so I started trying a few queries. As it turns out, the field is indeed set to 'Y', it's just not being displayed in the query output (or in the column within the application). I guess in my testing I was just focusing on the column output and ignoring the obvious of including that in the 'where' clause. I might give the 2.6.0 alpha a try and see what happens. Thanks!
File:
Bill, WR4MS
And it displays properly with the 2.6.0 alpha version. So I guess if anyone else runs into this issue, that's the fix.
73 de WR4MS
Bill, WR4MS
If you're unable to resolve the issue with CQRLOG, you might consider using alternative slice master logging software or seeking help from other ham radio enthusiasts who might have encountered similar issues.