Thanks for confirming Julian
> On Feb 14, 2024, at 7:11 PM, Julian Hyde wrote:
>
> 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
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
