[
https://issues.apache.org/jira/browse/CALCITE-525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16646032#comment-16646032
]
Vladimir Sitnikov commented on CALCITE-525:
-------------------------------------------
{quote} As I said, the SQL standard calls for certain built-in functions to
throw exceptions{quote}
Should those functions be isolated/catched instead?
For instance, we could implement "mysql mode" where 0/0 returns 0, and '30
February' is an acceptable date.
Just joking.
[~julianhyde], do you know other SQL implementations that implement that
"tolerant to division by zero" kind of mode?
I know OracleDB has "insert into DST select ... LOG ERRORS INTO ...", however
it works for errors like "trigger error on table DST" and/or "wrong datatype of
DST's column".
> Exception-handling in built-in functions
> ----------------------------------------
>
> Key: CALCITE-525
> URL: https://issues.apache.org/jira/browse/CALCITE-525
> Project: Calcite
> Issue Type: Bug
> Reporter: Julian Hyde
> Assignee: Hongze Zhang
> Priority: Major
>
> The standard calls for certain built-in functions to throw exceptions.
> Examples:
> * 1 / 0
> * MOD(1, 0)
> * OVERLAY('foo' PLACING 'x' FROM -1)
> * 'x' NOT LIKE 'x' ESCAPE 'x'
> First, these exceptions should occur at run time. They should cause the
> current value to become null, or the row to be omitted, but should not abort
> the query. (Actual behavior TBD.)
> Second, EnumerableCalc does constant reduction and generates code like
> 'static final int X = 0 / 0'. This code blows up when the class is loaded. It
> should not. The code should give errors for each row, as described above.
> While fixing this bug, see SqlOperatorBaseTest.testArgumentBounds and remove
> restrictions related to /, MOD and OVERLAY, LIKE.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
