Replies: 1 comment 4 replies
-
Ok. Thanks for letting me know. I'll confirm tomorrow and then dig into it. |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi Bruce,
We today noticed an error processing an example script, the single statement looks like it has been sectioned into multiple statements instead of just one.
We are using version 2.1.0.
Example input script:
SELECT CAST(123.45 AS INT), CAST(456.321 AS VARCHAR(10)), Column_1 FROM MyTable
Output:
`Statement 1: SELECT CAST ( 123.45 AS INT ) , CAST ( 456.321 AS VARCHAR 10
Token type: Keyword Text: SELECT
Token type: SystemIdentifier Text: CAST
Token type: Character Text: (
Token type: NumericLiteral Text: 123.45
Token type: Keyword Text: AS
Token type: Identifier Text: INT
Token type: Character Text: )
Token type: Character Text: ,
Token type: SystemIdentifier Text: CAST
Token type: Character Text: (
Token type: NumericLiteral Text: 456.321
Token type: Keyword Text: AS
Token type: Identifier Text: VARCHAR
Token type: NumericLiteral Text: 10
Statement 2: )
Token type: Character Text: )
Statement 3: ) , Column_1 FROM MyTable
Token type: Character Text: )
Token type: Character Text: ,
Token type: Identifier Text: Column_1
Token type: Keyword Text: FROM
Token type: Identifier Text: MyTable`
It looks like the parser has broken this single select into 3 statements and this caused execution part errored out as we execute based on the statements have been sectioned. This version 2.1.0 used to be working fine after fixing the missing "AS" in CAST statement in ver 2.0.1. It may be like that for some time already, but we only found out today.
I also tried ver 2.2.0, 2.2.1, the results are the same as above.
Could you please check if anything that may be causing this?
Thank you very much Bruce.
Regards
Paul
Beta Was this translation helpful? Give feedback.
All reactions