Replies: 1 comment 1 reply
-
|
Yes should be plenty safe enough to sql update |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello, I'm running CLoudLog v2.5.2 and I was testing the QSL label printing feature. Very good stuff!
I was surprised that my QSO from
IU5BON/IA5, correctly reported in the label printing page, showed up asIU5BONin the final PDF.Digging through the code I found that we are using
TABLE_HRD_CONTACTS_V01.COL_STATION_CALLSIGNto populate the PDF and searching the DB showed up some unexpected data in my CloudLog.How is it possible that those records have a
TABLE_HRD_CONTACTS_V01.COL_STATION_CALLSIGNthat does not match thestation_profile.station_callsign? I'm wondering if this is because of the ADIF import and CloudLog not overwriting the field when importing in a given station location.Can I safely issue an SQL UPDATE to clear the discrepancy?
Beta Was this translation helpful? Give feedback.
All reactions