FAQ
Answers to common questions. You can also find this section on the homepage.
FAQ
Quick answers to common questions about SQL Crack.
Can I paste my own SQL in the web demo?
Yes. Open /playground, paste your query, and click Visualize. Parsing happens entirely in your browser and your SQL is not sent to a backend.
Does SQL Crack send my SQL to a server?
No. The web demo parses SQL entirely in your browser, and the VS Code extension processes queries locally. Your SQL text is not uploaded or stored.
Which SQL dialects are supported?
MySQL, PostgreSQL, SQL Server, MariaDB, SQLite, Snowflake, BigQuery, Redshift, Hive, Athena, Trino, Oracle, and Teradata.
Is SQL Crack free to use?
Yes. The extension and website are free and open-source under the MIT license.
Does it work in Cursor, Windsurf, or other VS Code forks?
Yes. SQL Crack is available on OpenVSX (https://open-vsx.org/extension/buvan/sql-crack) and works in any editor that supports VS Code extensions.
What's the difference between the website and the extension?
The website playground lets you try SQL Flow without installing anything. The VS Code extension adds right-click visualization, multi-file workspace dependencies, and full dialect support. See the comparison table on the homepage for details.
Can it handle multiple queries in one file?
Yes. Both the web playground and the extension support multi-statement SQL. Paste multiple queries separated by semicolons — each gets its own tab. The extension also analyzes dependencies across multiple files in a workspace.
Does it support CREATE/DDL statements or only SELECT?
SQL Crack visualizes DML statements (SELECT, INSERT, UPDATE, DELETE) and shows DDL definitions like CREATE TABLE as schema blocks. The focus is on data flow — how queries read, transform, and write data.
Does SQL Crack support stored procedures?
Not currently. SQL Crack visualizes declarative SQL — data flow, not control flow. Stored procedures require dialect-specific procedural parsers, which is a fundamentally different problem.
Why does my query fail to parse in the web demo but work in the extension?
The web playground now uses the same full parser engine as the VS Code extension. If a query fails, it falls back to a simpler parser and then to pattern matching. Try selecting the correct dialect first. If parsing still fails, open an issue with the SQL sample.
How big can a query be before performance drops?
Most queries visualize instantly. Very large queries with many CTEs, deep nesting, or hundreds of columns may be slower in the browser due to memory and CPU limits. The VS Code extension handles large queries more efficiently.
How do I fix an incorrect lineage or graph result?
First, confirm you selected the correct dialect. Then try isolating the minimal SQL that produces the wrong result. If the web demo is wrong but the extension is correct, the web parser may not support that pattern yet. If both are wrong, open an issue with the SQL sample, selected dialect, and expected vs actual output.
Can I export results for docs or code reviews?
Yes. Export the flow diagram as PNG, SVG, Mermaid, or DOT (Graphviz) format. Export buttons are in the toolbar above the visualization panel. Use PNG for sharing, SVG for presentations, Mermaid for documentation, and DOT for Graphviz or draw.io.
How can I report a parser bug or request a dialect feature?
Open an issue at https://github.com/buva7687/sql-crack/issues with the SQL sample, selected dialect, and expected vs actual output. The more minimal the example, the faster the fix.
Where is the source code?
On GitHub: https://github.com/buva7687/sql-crack