Sometimes it happens that when Cqrlog is started it does not have any dates in QSO list.
If you do not have QSO list open you notice this when you are trying to save a new qso. Then you get a splash " "2022-11-06" is not valid date format". Date is the current date and it is in proper format.
Fix for this is to restart Cqrlog and usually that helps every time bringing dates back to QSO list.
Now when that again happened I tested a bit more with Cqrlog's SQL console.
Searching a qso directly from database fails too (command line mysql works OK with dates):
Getting just qsodate fails:
But adding zero (or any number) to qsodate brings it up, and this is amazing!
That makes me thinking is the bug really in Cqrlog or is it in FPC/ SQL unit?
Problem with this is that you cannot reproduce this, it just happens for every now and then.
Sometimes it happens that when Cqrlog is started it does not have any dates in QSO list.
If you do not have QSO list open you notice this when you are trying to save a new qso. Then you get a splash " "2022-11-06" is not valid date format". Date is the current date and it is in proper format.
Fix for this is to restart Cqrlog and usually that helps every time bringing dates back to QSO list.
Now when that again happened I tested a bit more with Cqrlog's SQL console.
Searching a qso directly from database fails too (command line mysql works OK with dates):
Getting just qsodate fails:
But adding zero (or any number) to qsodate brings it up, and this is amazing!
That makes me thinking is the bug really in Cqrlog or is it in FPC/ SQL unit?
Problem with this is that you cannot reproduce this, it just happens for every now and then.