In this article, the author explores some unexpected results that occur when working with InfluxQL functions in the SELECT statement, specifically when using the DISTINCT() function with the INTO clause and the GROUP BY time() clause. The behavior of these functions is explained by InfluxDB's internal workings, which can lead to surprising outcomes, such as missing data being written to a different measurement or timestamps not matching the original values. The author also discusses how the ELAPSED() function behaves when used with a nested function and a GROUP BY time() clause, resulting in consistent but incorrect results. These examples highlight the importance of understanding InfluxDB's functions and behavior to write effective queries.