Search found 312 matches
- 28 Sep 2020, 18:09
- Forum: User Support
- Topic: V1 not asking for mode switch
- Replies: 4
- Views: 2907
Re: V1 not asking for mode switch
IC-7300 but since it's via rigctld Log4OM won't know that.
- 28 Sep 2020, 17:51
- Forum: User Support
- Topic: V1 not asking for mode switch
- Replies: 4
- Views: 2907
V1 not asking for mode switch
Was working RTTY contest and also doing CW and Log4OM V1 was not always setting the mode. I'm using rigctld and can watch the commands coming across. Sometime it sets the mode and sometimes not. Can't seem to see any pattern. Is there some logic in Log4OM V1 that is trying be smart and not set mode ...
- 21 Sep 2020, 16:16
- Forum: Feature suggestions
- Topic: Email alert
- Replies: 7
- Views: 4344
Re: Email alert
Is this on the schedule to be implemented yet? I did submit some sample code for email in C# a while ago.
Thanks for all the work you guys do.
Mike W9MDB
Thanks for all the work you guys do.
Mike W9MDB
- 21 Sep 2020, 13:44
- Forum: Feature suggestions
- Topic: Slow queries
- Replies: 2
- Views: 2049
Re: Slow queries
JTAlert does a query which involves having to do "LIKE" on the qsoconfirmations field which is also a very slow query. What could be done is a single field for each logger type named like CONFIRMED_LOTW, CONFIRMED_EQSL, which is a boolean and correlates to the "R" field in qsocon...
- 24 Jun 2020, 16:29
- Forum: Feature suggestions
- Topic: Slow queries 2
- Replies: 9
- Views: 5694
Re: Slow queries 2
Also remember to add the index to callsign.
Mike
Mike
- 24 Jun 2020, 15:51
- Forum: User support
- Topic: QSL sent = No from JTAlert
- Replies: 22
- Views: 8144
Re: QSL sent = No from JTAlert
That's because nobody knows enough to complain....
I'm a developer so I know what to expect.
I'm a developer so I know what to expect.
- 24 Jun 2020, 13:58
- Forum: Feature suggestions
- Topic: Slow queries 2
- Replies: 9
- Views: 5694
Re: Slow queries 2
I don't see 2+ seconds running through the JSON fields as fast. Maybe not be as easy as a 2nd table...which would require multiple entries per QSL. It would link to the id field in the primary table and contain rows of QSL info for LOTW, EQsl, etc. So 8 rows per QSO....but comparitively short rows. ...
- 24 Jun 2020, 13:42
- Forum: User support
- Topic: QSL sent = No from JTAlert
- Replies: 22
- Views: 8144
Re: QSL sent = No from JTAlert
Well that's completely unintuitive to me...but you're right..that method does work. I thought the Select required would do the same...seems like you could get rid of the Select required and just use the Search and set the default Sent status when the Search confirmation is selected. One less button ...
- 24 Jun 2020, 13:28
- Forum: Feature suggestions
- Topic: Slow queries 2
- Replies: 9
- Views: 5694
Re: Slow queries 2
Hmmm...I wouldn't think 3 more tables would be needed. That might be over normalizing. Essentially it would be the same as the JSON structure but putting that in an indexed table that could be joined. So adding a new one wouldn't require any code changes at all....just a database update. At first bl...
- 24 Jun 2020, 12:58
- Forum: Feature suggestions
- Topic: Slow queries 2
- Replies: 9
- Views: 5694
Re: Slow queries 2
On another note about speed. The queries from JTAlert are like this on every decode (before JTAlert caches the info) select `qsodate` FROM `log` WHERE (`mode` LIKE ''FT8%'') AND (`band` = ''10m'') AND (`callsign`=''W1HS'') ORDER BY `qsoid` DESC; And one like this SELECT dxcc, cont, cqzone, ituzone, ...
