feat(ux): add Value.to_sql()

[NickCrews]

Is your feature request related to a problem?

often when debugging, I have some big expression like t.mutate().filter().order_by()

Then, when I need to look at the SQL, I need to wrap the whole thing as ibis.to_sql(...). Sometimes, this also requires a new import.

What is the motivation behind your request?

No response

Describe the solution you'd like

It would just be a nice UX if there was a chaining API, ie Value.to_sql() that just delegated to ibis.to_sql()

What version of ibis are you running?

main

What backend(s) are you using, if any?

I think it should still work to mix backends? eg ibis.duckdb.connect().table("x").mutate(y="z").to_sql(dialect="sqlite")

Code of Conduct

• I agree to follow this project's Code of Conduct

[gforsyth]

@jcrist - I have a memory of you having Thoughts (TM) on this method, but it could've been a fever dream.
Any objections to adding something like this?

[jcrist]

I'm +0 on this. Seems fine to add.

Tangent - I kinda don't like that we use to_* here, since in other cases the to_* methods all execute something (to_pandas, to_parquet, ..., see #9788). I was less concerned with ibis.to_sql, which is a top-level function. Adding a to_sql method to Table may confuse users since pandas also has a DataFrame.to_sql method which writes the frame out to a SQL database (similar to our other to_* methods. All that said, I don't think this is that big of a deal.