From 9cbfcd27d16c720b7068f3dda2b32e8178c8ee53 Mon Sep 17 00:00:00 2001
From: Bhargav <BJP232004@GMAIL.COM>
Date: Wed, 12 Jun 2024 15:34:19 +0530
Subject: [PATCH] fix: multiple timestamp columns displayed on result grid
 (#3723)

Issue : #3724
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

- **Bug Fixes**
- Improved accuracy in detecting timestamp columns in log queries,
ensuring more reliable data handling and display.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->
---
 web/src/composables/useLogs.ts | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/web/src/composables/useLogs.ts b/web/src/composables/useLogs.ts
index 928c55bf3c..dddbb53900 100644
--- a/web/src/composables/useLogs.ts
+++ b/web/src/composables/useLogs.ts
@@ -2188,7 +2188,7 @@ const useLogs = () => {
         if (
           (searchObj.meta.sqlMode == true &&
             parsedSQL.hasOwnProperty("columns") &&
-            hasTimeStampColumn(parsedSQL.columns)) ||
+            searchObj.data.queryResults?.hits[0].hasOwnProperty(store.state.zoConfig.timestamp_column)) ||
           searchObj.meta.sqlMode == false ||
           searchObj.data.stream.selectedFields.includes(
             store.state.zoConfig.timestamp_column
@@ -2230,7 +2230,7 @@ const useLogs = () => {
           if (
             (searchObj.meta.sqlMode == true &&
               parsedSQL.hasOwnProperty("columns") &&
-              hasTimeStampColumn(parsedSQL.columns)) ||
+              field == store.state.zoConfig.timestamp_column) ||
             field == store.state.zoConfig.timestamp_column
           ) {
             searchObj.data.resultGrid.columns.unshift({