You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello! Thank you for this great extension, I love how it helps me to experiment with SQL DBs without losing any valuable info by creating tons of files (on the screenshot you can see what a mess was that before I've found this extension, LOL).
I have one issue with COPY .. FROM .. WITH CSV statements with the PostgreSQL driver though. The problem is that the queries executed in the notebook can't reach the csv files in my filesystem, and I'm not sure what's the correct path. Using absolute path works, but it kinda defeats the point of having a shareable folder with SQLs in it.
Is there a possibility to determine what's the cwd of SQL script file or to set it automatically/manually? I think cwd being set to the folder of the current file is the most intuitive solution.
The text was updated successfully, but these errors were encountered:
Thanks for the detailed info. I'll need to take a closer look to see if we can expose this as an option. I'm surprised it isn't defaulting to the workspace dir. Maybe it's defaulting to the cwd of the postgresql server process?
Hello! Thank you for this great extension, I love how it helps me to experiment with SQL DBs without losing any valuable info by creating tons of files (on the screenshot you can see what a mess was that before I've found this extension, LOL).
I have one issue with
COPY .. FROM .. WITH CSV
statements with the PostgreSQL driver though. The problem is that the queries executed in the notebook can't reach the csv files in my filesystem, and I'm not sure what's the correct path. Using absolute path works, but it kinda defeats the point of having a shareable folder with SQLs in it.Is there a possibility to determine what's the
cwd
of SQL script file or to set it automatically/manually? I think cwd being set to the folder of the current file is the most intuitive solution.The text was updated successfully, but these errors were encountered: