tempusari commented on issue #2082: URL: https://github.com/apache/datafusion-sqlparser-rs/issues/2082#issuecomment-5414830833
Hi @ssteinhauser , I checked the syntax of the supported Oracle dialect against the Exasol SQL reference. On a first glance, mainly stuff like the `IMPORT` keyword and things like `CREATE SCRIPT [...]` and `EXECUTE SCRIPT [...]` are not part of the Oracle dialect. Which issues did you face when parsing Exasol SQL's with this software? If you want to contribute the dialect, open a PR. You can take a look at PRs that have added a dialect, e.g. this one #2380 which is still open for review for the Doris dialect. Also, even if your PR does not end up getting merged, you can always use your own fork and apply patches on top of it for your own use case. Since you are stating that you need this feature for the company you are working for, it should not be a problem to support your own contributions on your own fork. I would start by testing your SQL's using the Oracle dialect and once you have figured out which specific Exasol only features you are missing, you can start drafting your PR. I think this issue can be closed. Best regards -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
