Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
1.2.0
-
None
-
None
-
2018-16, 2018-17, 2018-18
Description
The following tests fail:
working_tpch1/qa_fe_cnxFunctions/addtime.sql - test doesn't support microseconds and add/sumtime negative error
working_tpch1/qa_fe_cnxFunctions/bug3333.sql - I think there are some behaviour issues here
working_tpch1/qa_fe_cnxFunctions/bug3334_ceil.sql - first query fails
working_tpch1/qa_fe_cnxFunctions/bug3334_overflow_error.negative.sql - no errors?!
working_tpch1/qa_fe_cnxFunctions/bug3584.sql - this might be correct behaviour now
working_tpch1/qa_fe_cnxFunctions/bug3585.sql - new behaviour is correct
working_tpch1/qa_fe_cnxFunctions/bug3792.negative.sql - subtime failure
working_tpch1/qa_fe_cnxFunctions/from_unixtime.sql - this might be due to my TZ
working_tpch1/qa_fe_cnxFunctions/STR_TO_DATE.sql - missing TIME datatype support
working_tpch1/qa_fe_cnxFunctions/subtime.sql - subtime failure
working_tpch1/qa_fe_cnxFunctions/TIMEDIFF.DM.sql - I think new behaviour is correct
working_tpch1/qa_fe_cnxFunctions/TIME.DS.sql - Need to check this one
working_tpch1/qa_fe_cnxFunctions/unix_timestamp.sql - Don't know
working_tpch1/qa_fe_postProcessedFunctions/SUBTIME.DM.sql - subtime error
working_tpch1/qa_fe_postProcessedFunctions/TIMEDIFF.DM.sql - I think new behaviour is correct
working_tpch1/aggregation/bitop.sql - appears to use internal datetime ints rather than external ones