xitep commented on issue #2065: URL: https://github.com/apache/datafusion-sqlparser-rs/issues/2065#issuecomment-3742476100
hello, i would like to share an experiment i've been working on (it's merely an educational effort for me to learn more about parsing and rust in general); i've tried coding the idea outlined by @RPG-Alex above with a ["toy crate"](https://crates.io/crates/orql) and it seems to work. [this example](https://docs.rs/orql/0.1.0/orql/parser/index.html#parsing-sql-into-an-ast-with-token-locations-and-comments) demonstrates the use-case. the crucial point is that `orql` exposes every token in its AST. but a fact is, that `orql` is merely a "toy." pushing it as far as `sqlparser` (limited to oracle sql), would be a _tons of work_ that i don't think is feasible for me. the question that i face now is whether i should invest my time into `orql` or `sqlparser`. would the concept of exposing every token in the AST be OK with `sqlparser`? -- 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]
