this in the discussion.)
Mihai
From: Julian Hyde
Sent: Monday, December 18, 2023 10:41 PM
To: dev@calcite.apache.org
Subject: Re: warnings in Calcite
I don’t think so. One place to surface warnings would be via
java.sql.Statement.getWarnings() but Avatica’s default
ses where at compile time an exception is thrown and caught could
> be warnings - e.g. Casts that will fail at runtime, division by 0, etc.
>
> Mihai
>
> From: Julian Hyde
> Sent: Monday, December 18, 2023 10:41:11 PM
> To: dev@calcite.apach
: warnings in Calcite
I don’t think so. One place to surface warnings would be via
java.sql.Statement.getWarnings() but Avatica’s default implementation of that
method returns null.
What are some scenarios where you think Calcite should give a warning?
Julian
> On Dec 18, 2023, at 7:13 PM, Mi
I don’t think so. One place to surface warnings would be via
java.sql.Statement.getWarnings() but Avatica’s default implementation of that
method returns null.
What are some scenarios where you think Calcite should give a warning?
Julian
> On Dec 18, 2023, at 7:13 PM, Mihai Budiu wrote:
>
Does calcite have any facilities for reporting warnings to users?
Thank you,
Mihai
Julian Hyde created CALCITE-3102:
Summary: Deprecation warnings following [CALCITE-2969]
Key: CALCITE-3102
URL: https://issues.apache.org/jira/browse/CALCITE-3102
Project: Calcite
Issue Type