Map Oracle date to Trino timestamp(0) type

[ebyhr]

Fixes #10626

[ebyhr]

Unfortunately, it's little hard to verify the Oracle execution plan on CI at this time. Here is the manual comparison results:

Create index on TPCH orders.orderdate column.

CREATE INDEX trino_test_orders ON trino_test.orders (orderdate);

TO_TIMESTAMP function

EXPlAIN PLAN FOR SELECT * FROM trino_test.orders WHERE orderdate > TO_TIMESTAMP('2011-01-01 01:01:01.11"', 'SYYYY-MM-DD HH24:MI:SS.FF');
SELECT PLAN_TABLE_OUTPUT FROM TABLE(DBMS_XPLAN.DISPLAY()); 

Plan hash value: 1275100350
 
----------------------------------------------------------------------------
| Id  | Operation         | Name   | Rows  | Bytes | Cost (%CPU)| Time     |
----------------------------------------------------------------------------
|   0 | SELECT STATEMENT  |        |   779 |   214K|    70   (3)| 00:00:01 |
|*  1 |  TABLE ACCESS FULL| ORDERS |   779 |   214K|    70   (3)| 00:00:01 |
----------------------------------------------------------------------------
 
Predicate Information (identified by operation id):
---------------------------------------------------
 
   1 - filter(INTERNAL_FUNCTION("ORDERDATE")>TO_TIMESTAMP('2011-01-01 
              01:01:01.11"','SYYYY-MM-DD HH24:MI:SS.FF'))
 
Note
-----
   - dynamic sampling used for this statement (level=2)

TO_DATE function

EXPlAIN PLAN FOR SELECT * FROM trino_test.orders WHERE orderdate > TO_DATE('2011-01-01 01:01:01.11"', 'SYYYY-MM-DD HH24:MI:SS.FF');
SELECT PLAN_TABLE_OUTPUT FROM TABLE(DBMS_XPLAN.DISPLAY()); 

Plan hash value: 1158690668
 
-------------------------------------------------------------------------------------------------
| Id  | Operation                   | Name              | Rows  | Bytes | Cost (%CPU)| Time     |
-------------------------------------------------------------------------------------------------
|   0 | SELECT STATEMENT            |                   |   997 |   274K|    67   (0)| 00:00:01 |
|   1 |  TABLE ACCESS BY INDEX ROWID| ORDERS            |   997 |   274K|    67   (0)| 00:00:01 |
|*  2 |   INDEX RANGE SCAN          | TRINO_TEST_ORDERS |   179 |       |     2   (0)| 00:00:01 |
-------------------------------------------------------------------------------------------------
 
Predicate Information (identified by operation id):
---------------------------------------------------
 
   2 - access("ORDERDATE">TO_DATE('2011-01-01 01:01:01.11"','SYYYY-MM-DD HH24:MI:SS.FF'))

[findepi]

@hashhar ptal

[ebyhr]

@hashhar Gentler reminder. I would like to include this PR into 369 because it's kind of regression in 368.

[hashhar]

Some comments. Looks good overall.

Will this break any views people have created using Hive connector over Oracle tables?

[ebyhr]

Will this break any views people have created using Hive connector over Oracle tables?

It won't break existing views. The original column definition timestamp(3) would be respected unless they re-create views.