I kept getting rusty on SQL syntax between projects and got tired of AI tools that would confidently make up a column name rather than admit they didn't know it. That's really what inspired this. I wanted something that checks itself against a real schema instead of guessing. As I built it, the approach kept shifting toward safety and honesty rather than just "generate SQL fast." I added a row-impact preview so you can see how many rows a DELETE or UPDATE will actually touch before running it, and I made sure it tells you plainly when it can't find a column instead of inventing one. I also tested every feature by hand before shipping, which caught a few real bugs along the way including one where a safety-check query had an empty WHERE clause and would've been useless if I hadn't caught it. Would love to hear what's useful here and what's missing.

SQLGenie

Turn plain English into SQL with safety checks

Turn plain English into SQL with safety checks