Teradata SQL Grammar #4330
Teradata SQL Grammar #4330
Conversation
| @@ -0,0 +1,31 @@ | |||
| # Teradata SQL Grammar | |||
|
|
|||
| An [ANTLR4](https://www.antlr.org/) grammar for Teradata SQL. Based on a grammar of Teradata Database version 17.10. | |||
There was a problem hiding this comment.
Please include a permalink to the actual grammar for version 17.10. Is it a bison grammar? Is there a lex file?
| numeric_data_type | ||
| : BYTEINT | ||
| | SMALLINT | ||
| | (INTEGER|INT) |
There was a problem hiding this comment.
Parentheses are used in places that don't need them. Why? E.g., (INTEGER | INT) instead of INTEGER | INT.
| cursor_declaration* | ||
| condition_handler* | ||
| procedure_stat* | ||
| END (label_name)? |
There was a problem hiding this comment.
Ditto on (label_name)?. Why this instead of label_name??
| (ON logging_item (',' logging_item)* )? | ||
| ; | ||
|
|
||
| operation |
There was a problem hiding this comment.
Please sort and uniq this list. You have duplicates, which is causing ambiguity to be detected in examples/ddl/logging/begin_logging.sql. For example, two INSERT, two SELECT, two UPDATE.
|
(On the build, the MacOS runners in GitHub are terrible--hanging in the testing for Java. I'm not sure when they will finish, but it's stalled in parsing for the Java target. But, that works in about 9s on my machine just fine. My PR #4327 removes the parsing tests for MacOS in order to minimize hangs like this from happening.) |
Grammar of Teradata SQL dialect based on version 17.10 of Teradata Vantage.
Based on my estimates, this grammar is 90% complete. We used it to parse codebase of tens of thousands of objects for enterprise data lineage.
I've started to add examples only at a later stage of the development, so
examplesdir lacks many essential statements, like CRUD.Q: Why "Teradata SQL" is in naming, not just "Teradata"?
A: I've made it deliberately, because this grammar covers only SQL, without BTEQ scripting language (I think BTEQ scripts should have separate grammar).