From 70e011ff900792fe7d824826d6b7623afb2c6c1b Mon Sep 17 00:00:00 2001 From: Alexey Milovidov Date: Sun, 18 Dec 2022 04:58:51 +0100 Subject: [PATCH] Add a test for PowerBI --- .../0_stateless/02503_mysql_compat_utc_timestamp.reference | 0 tests/queries/0_stateless/02503_mysql_compat_utc_timestamp.sql | 2 ++ 2 files changed, 2 insertions(+) create mode 100644 tests/queries/0_stateless/02503_mysql_compat_utc_timestamp.reference create mode 100644 tests/queries/0_stateless/02503_mysql_compat_utc_timestamp.sql diff --git a/tests/queries/0_stateless/02503_mysql_compat_utc_timestamp.reference b/tests/queries/0_stateless/02503_mysql_compat_utc_timestamp.reference new file mode 100644 index 00000000000..e69de29bb2d diff --git a/tests/queries/0_stateless/02503_mysql_compat_utc_timestamp.sql b/tests/queries/0_stateless/02503_mysql_compat_utc_timestamp.sql new file mode 100644 index 00000000000..fa327a38f21 --- /dev/null +++ b/tests/queries/0_stateless/02503_mysql_compat_utc_timestamp.sql @@ -0,0 +1,2 @@ +-- PowerBI is doing this query. It should work at least somehow, not necessarily in the same way as in MySQL. +SELECT TIMEDIFF(NOW(), UTC_TIMESTAMP());