Eduardo Blancas

goot catch! this indeed looks like a bug, note that we have a `--no-execute` flag so in that case, users could save broken snippets. but if the flag isn't present,...

@ned2: thanks for working on this! I ran some quick tests, and here are my thoughts. You're on the right track; I think the best place to apply this change...

thanks for catching this error. this is a bit challenging because the resolution order is important. I think we can keep this open and tackle it once we finish other...

@mehtamohit013 any updates?

as long as we cover duckdb and postgres, it's fine. let's see what error does duckdb and postgres show. then implement logic that when it detects this issue, it adds...

I don't understand why we can't use the exceptions You can catch the exception and see if the error message matches a specific pattern. If so, you can handle each...

so this one needs a bit more investigation. currently, jupysql supports sqlalchemy 1.x and sqlalchemy 2.x. we also support psycopg2 my conclusion from some initial research is that with this...

ok, can you see if jupysql works with psycopg3? my guess is that you'd need sqlalchemy 2 (which we support). I think let's first find out about psycopg3 and then...

yes, you need to connect to a database and run a few queries. you can use this as a reference: https://jupysql.ploomber.io/en/latest/integrations/postgres-connect.html just modify the connection string and ensure it uses...

> you need to connect to a database and run a few queries.