-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Relative paths behave differently with spatial extension than with others #308
Labels
Comments
Hi! Thanks for reporting this issue. |
Weird!! Might be on my end then. I'm on MacOS indeed, latest version. I installed the latest duckdb via homebrew, and ran:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Example:
GDB data:
DuckDB usage:
The above works, but with read_csv and others, relative paths are accepted. (Was getting uninformative errors when using
SELECT * FROM ST_READ('~/data/nyc_mappluto_24v1_fgdb/MapPLUTO24v1.gdb')
as I am more used to DuckDB vs spatial duckdb syntax)Thank you for an awesome extension!! It's leading to this: https://jaanli.github.io/new-york-real-estate/
The text was updated successfully, but these errors were encountered: