Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

User changes DXCC, what then? #460

Open
OH1KH opened this issue Nov 18, 2021 · 0 comments
Open

User changes DXCC, what then? #460

OH1KH opened this issue Nov 18, 2021 · 0 comments

Comments

@OH1KH
Copy link
Contributor

OH1KH commented Nov 18, 2021

Could someone, please, tell me the purpose of column "qso_dxcc.cqrlog_main" ?

If user enters new qso call., let's say KP2B and uses HamQTH callbook support, he will get DXCC KP4 (Puerto RIco). That is wrong as HamQTH holds old wrong information.
User notices that and changes DXCC to KP2 (Virgin islands) before saving qso.

When qso is saved and he views qso again he sees that KP2B is logged as DXCC=KP4 even he has changed it before saving.

If we then look at database content of that qso we can see that column "qso_dxcc"(bolean) has got value 1(True) while normal, not DXCC edited qsos have all value 0.
This "qso_dxcc" is also called "changed" inside procedures.

It seems to indicat that user has touched DXCC.
OK, so far but what we do with that information as the adif value of qso is still the original and not the one that user has changed it to ?
It looks like "qso_dxcc" has been, or was sometimes planned to be, indicator of edited DXCC. Has the part of adif change source removed, or newer written yet?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant