%7N is not valid, it will support %9N and parse the 7 digit timestamp data correctly including the time zone, but %9N is actually broken in that it will ONLY recognise microseconds (6 places) See th...
See more...
%7N is not valid, it will support %9N and parse the 7 digit timestamp data correctly including the time zone, but %9N is actually broken in that it will ONLY recognise microseconds (6 places) See this example where nanoseconds 701 and 702 are in two fields - when parsed and reconstructed, the times are the same with only microseconds | makeresults
| eval time1="2024-11-25T01:45:03.512993701-05:00"
| eval time2="2024-11-25T01:45:03.512993702-05:00"
| eval tester_N=strptime(time1, "%Y-%m-%dT%H:%M:%S.%9N%:z")
| eval tt_N=strftime(tester_N, "%Y-%m-%dT%H:%M:%S.%9N%:z")
| eval tester_N2=strptime(time2, "%Y-%m-%dT%H:%M:%S.%9N%:z")
| eval tt_N2=strftime(tester_N2, "%Y-%m-%dT%H:%M:%S.%9N%:z")
| eval isSame=if(tester_N2=tester_N,"true","false")