Maybe in the next version they could also implement support for DROP, with autocorrect for the nearest (not yet dropped) table name.

LLM powered queries that run in Agent mode so it can answer questions of your data before you know what to ask.

That's actually not a bad idea, to have LLM autocomplete when you write queries, especially if you first add a comment at the top saying what you want to achieve:

// Select all orders for users registered in last year, and compute average earnings per user

SELECT ...

That already works in windsurf, I’ve created unit tests in go, where I just wrote a short comment in the unit test what data to query and windsurf would autocomplete with the full sql.

I mean, all LLMs do this already, but I never saw LLM autocomplete in a db tool (e.g. phpmyamdin, MongoDB Compass, etc).

Vibe SQLing is where it's at

DELETED 0 rows. Did you mean `where 1=1`? (click accept to re-run with new where clause)

Or, for extra fun, it auto completes to DROP TRIGGER and just drops a single random trigger from your database. It'll help counter automation fears by ensuring your DBAs get to have a wonderful weekend on payroll where, very much in the easter spirit, they can hunt through the DB looking for the one thing that should be there but isn't!

Wow, that's perhaps the most nefarious version of chaos engineering I had ever heard of. Kudos!

for clarity: Instant SQL won't automatically run queries that write or delete data or metadata. It only runs queries that read data.

And this is a happy coincidence that json_serialize_sql doesn't work with anything but select queries

Young bobby tables at it again

Can't it just run inside a transaction that isn't committed?

ROFL

ROFL FROM jokes WHERE thats_a_new_one;