SQL[CRUD]-to-text

I didn't realize that “SQL-to-Text” can only translate SELECT statements!

Until I tried to explain a complicated INSERT query that a user needed to confirm inside an annotation tool… and the models - HuggingFaceH4’s zephyr-7b-beta, Google’s T5 (even the fine-tuned mrm8488/t5-base-finetuned-wikiSQL) just answered: “What ...?” (as “what to SELECT?”).

That’s when I discovered - AI don’t even understand the basic SQL statements:

𝐂reate (Insert) → add new records into a table;

𝐑ead (Select) → read existing records;

𝐔pdate → change existing records;

𝐃elete → remove records.

To bridge this gap, I built a prompt-based solution per SQL statement. Each prompt tells the model what the statement really means, and then guides token generation - so the final output isn’t just a translation of syntax, but a clear explanation of what that specific query will do.

This way, annotators and users of different SQL levels can approve (or reject) queries in plain English and all teams align faster in project details without getting stuck in syntax details.

(CRUD)SQL-to-Text turns most complex queries into very simple insights and let us spend less time explaining SQL and more time deciding!

Try CRUD-SQL2Text workaround in action: https://lnkd.in/dQXbhftY