From f9ab2f7293577c089ef2cb48e31337938030fe55 Mon Sep 17 00:00:00 2001 From: Joseph Doherty Date: Sun, 11 Oct 2026 10:44:15 -0400 Subject: [PATCH] fix(questdb): #678.4 distinguish cleared vs applied TTL log wording --- .../QuestDbSchemaBootstrapper.cs | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/src/Drivers/ZB.MOM.WW.OtOpcUa.Driver.Historian.QuestDb/QuestDbSchemaBootstrapper.cs b/src/Drivers/ZB.MOM.WW.OtOpcUa.Driver.Historian.QuestDb/QuestDbSchemaBootstrapper.cs index 296f787d..f610fac5 100644 --- a/src/Drivers/ZB.MOM.WW.OtOpcUa.Driver.Historian.QuestDb/QuestDbSchemaBootstrapper.cs +++ b/src/Drivers/ZB.MOM.WW.OtOpcUa.Driver.Historian.QuestDb/QuestDbSchemaBootstrapper.cs @@ -137,7 +137,10 @@ internal sealed class QuestDbSchemaBootstrapper // The ALTER is a WAL transaction: tables() keeps the old value until it applies, so do NOT re-read to verify. await using (var alter = _conn.CreateCommand(conn, QuestDbTables.AlterTtl(table, _options.RetentionDays))) await alter.ExecuteNonQueryAsync(ct).ConfigureAwait(false); - _log.LogInformation("Applied TTL {Days} day(s) to QuestDB table {Table}.", _options.RetentionDays, table); + if (_options.RetentionDays is { } days) + _log.LogInformation("Applied TTL {Days} day(s) to QuestDB table {Table}.", days, table); + else + _log.LogInformation("Cleared TTL on QuestDB table {Table}.", table); } } }