3 ms·
yes, apologies, I skipped ahead. Parsing: "There’s not very many instances where someone needs to parse sql" The only use cases would be building your own data
by bfung 4y ago
yes, apologies, I skipped ahead.
Parsing: "There’s not very many instances where someone needs to parse sql"
The only use cases would be building your own database/query optimizer and having SQL be the API.
There are plenty of other tools already to help programming languages interface w/SQL, give compile time checks, test, generate SQL, etc.
Build the parser for fun, sure, but don't then offer consulting services on an article that didn't really specify a business problem or outcome and just talked about tech stuff.
- zasdffaa 4y agoHe actually lists at the end as an alternatives to his consulting: Consider if you can use existing tools or libraries to process SQL code. Some of them even support multiple SQL-dialects or multiple programming languages. If you can use any of them for your needs they should be your first option If you want to build a solution in-house you may consider starting from the few ANTLR grammars available for the major SQL databases. They can really help you get started in parsing SQL > There are plenty of other tools already to help ... give compile time checks Which are these? > ..that didn't really specify a business problem or outcome and just talked about tech stuff. The business problem is to build an sql parser. the outcome being an SQL parser. It's clear enough and it's something I had to do. Your criticisms are unreasonable.