exa-IDEAS
Community Manager
Community Manager

Preface

While the sqlparsing library provided by Exasol does a good job in tokenizing (SQL) text and locating given search patterns within those tokens, it does not provide context or semantic information for SQL.
The latter would be very useful for some of the more complex use cases.

Request

Similar to the pushdown specification of virtual schemas (see https://github.com/EXASOL/virtual-schemas/tree/master/doc#pushdown), add a possibility to retrieve a structured representation of a given SQL text (assuming that it is indeed compliant with our parser).
JSON would be one candidate for structuring, should IDEA-344 get implemented.

Use Cases

  • For implementing IDEA-359: Produce a list of (table-) dependencies for a given statement
  • Extension of the above: Produce a list of input- and output-columns for a given statement ("Data Lineage")
  • Less error-prone preprocessor scripts

 

Migrated from IDEA-376 by @exa-StefanR 

https://www.exasol.com/support/browse/IDEA-376

 

2 Comments
Status changed to: Migrated
exa-IDEAS
Community Manager
Community Manager
 
Status changed to: Comments Requested
exa-Tobias
Team Exasol
Team Exasol

@exa-StefanR Do I understand it correctly, that this idea would be obsolete if Eaxsol would provide data-linage on an sql-text?