It's not unexpected. :)
Would you expect us to require whitespace between one token and the
next? If you write '(1+2)' there are five tokens, no whitespace
required.
By the way, Postgres seems to do the same as Calcite.
On Wed, Feb 14, 2024 at 6:13 PM Sean Broeder wrote:
>
> It looks like
It looks like Calcite converts "SELECT 1000L" into "SELECT 1000 AS 'L' " in
SqlParserImpl.UnsignedNumericLiteral. Is this expected? Note, there is no
space between 1000 and L in the original statement.
Thanks,
Sean
Tim Nieradzik created CALCITE-6265:
--
Summary: Cannot provide different numeric type as placeholder
Key: CALCITE-6265
URL: https://issues.apache.org/jira/browse/CALCITE-6265
Project: Calcite
Bertil Chapuis created CALCITE-6264:
---
Summary: Implement ST functions for the TWKB format
Key: CALCITE-6264
URL: https://issues.apache.org/jira/browse/CALCITE-6264
Project: Calcite
Issue
Bertil Chapuis created CALCITE-6263:
---
Summary: Discuss the coupling of Calcite with JTS
Key: CALCITE-6263
URL: https://issues.apache.org/jira/browse/CALCITE-6263
Project: Calcite
Issue