New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Restore datetime functions in SQL #4898
Comments
That's SQLite syntax. The original is
(substituting '71' for '[DELTA]' as allowed by 2.4.1.3) |
Yup, I know, but such modifications are allowable to be made by vendor to complete queries. In a longer run we will return vanilla syntax, but today we are interested to compare against SQLite. To measure the baseline. If you are curios - look here https://github.com/tsafin/tnt-tpch/blob/master/execute_query.lua (do not be confused with README, I've not yet updated it) |
Waiting till tarantool/tpch#1 be resolved before transferring to QA |
Commit #3caeb33cdaf4b37974fd5f12e08310502d9e73f3 has disabled DATETIME support in Tarantool SQL. Now we are restoring it to make possible to run TPC-H queries. We restore functions and they will use underlying STRING type, instead of actual date types. This is better than nothing for today. We will complete actual date/datetime types support once DECIMAL type will land here. Closes tarantool#4898
Commit #3caeb33cdaf4b37974fd5f12e08310502d9e73f3 has disabled all datetime tests. Now, having restored datetime functions support we revert it, and restore sql testing for those functions Closes tarantool#4898
If it is true that "in a longer run we will return vanilla syntax", |
AFAIU, the issue is resolved in scope of this commit. Closing then. |
15 out of 22 TPC-H queries use some sort of datetime functions, .e.g. q1.sql
at the moment it's disabled in src/sq/date.c
WE need to restore them, becase they block #2903 TPC-H benchmarks.
The text was updated successfully, but these errors were encountered: