I’m surprised we don’t support INTEGER to DECIMAL, since it is lossless (unlike, say, converting from INTEGER to REAL). Though I don’t recall what the SQL standard says about that conversion.
It is reasonable to be able to call the GIS functions with integer arguments. Julian > On Nov 5, 2019, at 4:21 AM, Kirils Mensikovs <[email protected]> wrote: > > > Here is JIRA ticket: > https://issues.apache.org/jira/browse/CALCITE-3477 > > If you can point me where can I fix it, it would be nice. > > Thanks, > -Kiril > >> On Nov 4, 2019, at 9:41 PM, Julian Hyde <[email protected]> wrote: >> >> Can you log a bug, please? >> >>> On Nov 1, 2019, at 5:01 AM, Kirils Mensikovs <[email protected]> wrote: >>> >>> Hi, >>> >>> I am using ST_MakePoint(1.0, 1.0) and that works fine. However, when I try >>> to run following command ST_MakePoint(1, 1), I got exception: >>> `No applicable constructor/method found for actual parameters "int, int”` >>> >>> How to automatically cast int to BigDecimal? >>> >>> Thanks, >>> -Kiril >> >
