View Revisions: Issue #2062

Summary 0002062: Logbook performance is poor with a large database
Revision 2017-08-16 16:52 by WA9PIE
Steps To Reproduce 1) Open the logbook; debug build in the debugger
2) Open a large database
3) Double-click any log entry to get an ALE
4) I the ALE window, activate the "Worked" tab
5) after a pause, the Worked tab will populate.

The pause is because the database is being asked to scan all the rows in the large database you've opened.

The debugger logs the queries, they are here:

2017-06-21 16:13:39: ALE:Worked:Refresh: Call="KC3DS", Country="United States"
2017-06-21 16:13:39: LOG> WorkedStatusEx, Select: (COL_CALL = 'KC3DS') OR (COL_CALL LIKE '%/KC3DS/%') OR (COL_CALL LIKE '%/KC3DS') OR (COL_CALL LIKE 'KC3DS/%')
LogfileView.cpp(231) : atlTraceGeneral - SHOW> DBG 1, WorkedStatusEx, Select: (COL_CALL = 'KC3DS') OR (COL_CALL LIKE '%/KC3DS/%') OR (COL_CALL LIKE '%/KC3DS') OR (COL_CALL LIKE 'KC3DS/%')
LogbookFullLookup.cpp(147) : atlTraceGeneral - Callsign "KC3DS" = KC3, KC3DS,


Revision 2017-06-21 18:22 by K7ZCZ
Steps To Reproduce
1) Open the logbook; debug build in the debugger
2) Open a large database
3) Double-click any log entry to get an ALE
4) I the ALE window, activate the "Worked" tab
5) after a pause, the Worked tab will populate.

The pause is because the database is being asked to scan all the rows in the large database you've opened.

The debugger logs the queries, they are here:

2017-06-21 16:13:39: ALE:Worked:Refresh: Call="KC3DS", Country="United States"
2017-06-21 16:13:39: LOG> WorkedStatusEx, Select: (COL_CALL = 'KC3DS') OR (COL_CALL LIKE '%/KC3DS/%') OR (COL_CALL LIKE '%/KC3DS') OR (COL_CALL LIKE 'KC3DS/%')
LogfileView.cpp(231) : atlTraceGeneral - SHOW> DBG 1, WorkedStatusEx, Select: (COL_CALL = 'KC3DS') OR (COL_CALL LIKE '%/KC3DS/%') OR (COL_CALL LIKE '%/KC3DS') OR (COL_CALL LIKE 'KC3DS/%')
LogbookFullLookup.cpp(147) : atlTraceGeneral - Callsign "KC3DS" = KC3, KC3DS,