[
https://issues.apache.org/jira/browse/CALCITE-4531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17305951#comment-17305951
]
Vladimir Sitnikov commented on CALCITE-4531:
--------------------------------------------
BigQuery uses INT64 for LIMIT and OFFSET:
https://cloud.google.com/bigquery/docs/reference/standard-sql/query-syntax#limit_and_offset_clause
{quote}LIMIT specifies a non-negative count of type INT64, and no more than
count rows will be returned. LIMIT 0 returns 0 rows.
If there is a set operation, LIMIT is applied after the set operation is
evaluated.
OFFSET specifies a non-negative number of rows to skip before applying LIMIT.
skip_rows is of type INT64.{quote}
> Deprecate RexLiteral#intValue since it performs silent truncation
> -----------------------------------------------------------------
>
> Key: CALCITE-4531
> URL: https://issues.apache.org/jira/browse/CALCITE-4531
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Reporter: Vladimir Sitnikov
> Priority: Critical
>
> {{RexLiteral#intValue}} is prone to errors since it silently truncates values
> to {{int}} so the developers might fail to know that at the compile time.
> It might be safer to expose {{BigDecimal}} or {{intValueExact}} or
> {{doubleValue}} alternatives which would be "enough for all the possible
> cases".
> An alternative option is to mark the method as deprecated, so every use of
> the method would require users to suppress the warning, so they know why the
> method is deprecated.
> I guess the most common use case for {{RexLiteral.intValue}} is {{offset}}
> and {{fetch}} in {{Sort}}, however, the misuse is hard to spot, and it might
> result in hard to notice data corruptions.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
