On another note about speed. The queries from JTAlert are like this on every decode (before JTAlert caches the info) select `qsodate` FROM `log` WHERE (`mode` LIKE ''FT8%'') AND (`band` = ''10m'') AND (`callsign`=''W1HS'') ORDER BY `qsoid` DESC; And one like this SELECT dxcc, cont, cqzone, ituzone, ...

The debug log doesn't show the total time...just the query time. I've got over 34,000 QSOs in the log. The actual query I've tested and by itself takes a little over 2.5 seconds evenly split between query and fetch according to MySQL Workbench timing. In order to get any QSL status in this database ...

My point Terry is that I shouldn't have to change the configuration to select something other than the default and that the default should not be forced when Select Required is clicked. If you can't change it why have a pulldown at all? Isn't that the point of a pulldown to select from multiple valu...

Oops...let me correct that...still broken... The pull down box on the left side is set to whatever the selection is in Confirmations when you click Select required. I could see setting the default when you pick LOTW as the Search Confirmation...but not when you click Select required. And I'd like to...

It seems a fresh download and install-over-the-top did fix it.
Seems odd but I'll have my friend try it too.

Thanks Terry,

Mike

The left side.
Click the left side pulldown to a non-default and click the "Sent" box. Then click "Select required" -- the box turns back to the default so the pulldown is useless.

Mike

If you're not going to fix the pulldown in the QSL manager so we can select a status other than the default for LOTW you should at least make the box read only since it apparently has no effect. Then all the users would have to do is try and figure out how to fix their problem. Or do you think it sh...

No...we did not change that. We were trying to fix a batch of QSO where the status was wrong. Both of your suggestions for workarounds work...but that's not desirable behavior when the fix is to make the Snet pulldown work correctly for choosing LOTW sent status. And is the text in that box wrong or...

Doesn't work on his computer or mine. Both of us using 2.7.0 I have one QSO that I marked as "Requested" for LOTW sent status and it queries just fine as Requested. Change that QSO to LOTW Sent "No", click the Sent pulldown for No, click "Select required" and the pullldown box changes back to Reques...

The LOTW upload query is a good example of the lack of normalization in the database. This query has to retrieve the entire database so it can parse the QSL field for LOTW QSO's to upload. This same every-qsl-in-a-field-regardless-of-source also slows down other queries. The lot Log4OM does this sam...