Re: ToDo item: switch logfile to database

[Thomas Beierlein]

Hi, see below:

Am Fri, 29 Dec 2023 03:20:05 +0000
schrieb Drew Arnett <arnett.drew@gmail.com>:

> tangent:  Variable length fields are handled easily with line
> separators delimiting records and space, comma, tab delimiting fields
> in a record.  It may be the UI (especially a TUI) where expected max
> field length may have value.  

Variable field length results in variable length of qso record.
That makes editing/updating old entries more complex. As soon as you
get a longer entry you need to make room in the file. That requires a
lot more disk activity (and a higher chance of corruption) than just do
a modification 'in place' and that is what we do at the moment.

A database has the same problem but there was much more done to
keep the data save in case of a crash.

> For example, what's the maximum length
> callsign 

TLF supports 12 or 13 characters if I remember correctly.
 
> I might expect to encounter in a contest or operating event
> where I'd use tlf?  Is there a safe maximum length to use for callsign
> length?  Prefixes and suffixes and some of those special event
> callsigns make me wonder.  Does ITU have anything to say, or is there
> no upper bound to possible callsign length?
> 

> tangent:  Internationalization... unicode text file for log certainly
> would work.  ASCII would suffice for the contests I participate in
> including CQ WW.  However, if not difficult, internationalization may
> be a nice to have for folks who would want it, but perhaps not high
> priority.  

I agree that it has no high priority for actual contesting.

The interesting part may not be the call but that someone would like
to add some comments in its non ascii language.

73, de Tom DL1JBE



-- 
"Do what is needful!"
Ursula LeGuin: Earthsea
--