Mercurial > dovecot > core-2.2
changeset 22432:aff38b5d7f1f
cassandra: Fix confusing debug logging for paged query results.
Even when caller supported paged queries, the debug output contained
"Paged query has more results, but not supported by the caller".
Clear out the error after sql_result_more() is called, so it won't be
logged.
| author | Timo Sirainen <timo.sirainen@dovecot.fi> |
|---|---|
| date | Mon, 14 Aug 2017 15:44:24 +0300 |
| parents | 691b5466edb3 |
| children | 47389f0e1827 |
| files | src/lib-sql/driver-cassandra.c |
| diffstat | 1 files changed, 3 insertions(+), 0 deletions(-) [+] |
line wrap: on
line diff
--- a/src/lib-sql/driver-cassandra.c Sun Jul 02 12:05:36 2017 +0200 +++ b/src/lib-sql/driver-cassandra.c Mon Aug 14 15:44:24 2017 +0300 @@ -1296,6 +1296,9 @@ cass_statement_set_paging_state(new_result->statement, old_result->result); old_result->paging_continues = TRUE; + /* The caller did support paging. Clear out the "...not supported by + the caller" error text, so it won't be in the debug log output. */ + i_free_and_null(old_result->error); new_result->page_num = old_result->page_num + 1; new_result->page0_start_time = old_result->page0_start_time;