Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
Make type conversion documentation consistent with behavior and tests. Use the following steps:
* Create an internal map that, for each pair of data types, says whether conversion is implicit, explicit, or disallowed
* Run tests based on that map
* In DocumentationTest, generate an HTML table of that mapping, and check that that table is consistent with the one in the SQL reference.
I know of two errors in the table:
* The table says that you can explicitly cast from INT to TIMESTAMP (see CALCITE-5483); this should be disallowed;
- The table says that you can explicitly cast from DECIMAL to BOOLEAN (see
CALCITE-4777); this should be disallowed.
There may be others.
Attachments
Issue Links
- is related to
-
CALCITE-3311 Add doc to site for implicit type coercion
- Closed
-
CALCITE-3053 Add a test to ensure that all functions are documented in the SQL reference
- Closed
-
CALCITE-4777 Casting from DECIMAL to BOOLEAN throws an exception
- Closed
-
CALCITE-5483 ProjectAggregateMergeRule throws exception if literal is non-numeric
- Closed