Change RST fields to strings #6

Open
opened 3 years ago by dj1yfk · 0 comments
dj1yfk commented 3 years ago
Owner

There are many use cases where the RST field should accept more than just an integer value:

  • FT8 reports (e.g. -12)
  • RST reports with additional info like 599A (Aurora)
  • Various contest exchanges

The current ADIF standard (3.11) also defines the RST field as a string, so this should be changed in YFKlog.

This includes at least the following changes:

  • Change the database definition for RSTS and RSTR from int to varchar (which length?)
  • Change validation for entering RSTs from [0-9] to a sensible set of characters
  • Change validation in ADIF import
    ...
There are many use cases where the RST field should accept more than just an integer value: * FT8 reports (e.g. -12) * RST reports with additional info like 599A (Aurora) * Various contest exchanges The current ADIF standard (3.11) also defines the RST field as a string, so this should be changed in YFKlog. This includes at least the following changes: * Change the database definition for RSTS and RSTR from int to varchar (which length?) * Change validation for entering RSTs from [0-9] to a sensible set of characters * Change validation in ADIF import ...
Sign in to join this conversation.
No Label
No Milestone
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.