Skip to content
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

potential confusion points #1

Open
ajfriend opened this issue Sep 25, 2022 · 1 comment
Open

potential confusion points #1

ajfriend opened this issue Sep 25, 2022 · 1 comment

Comments

@ajfriend
Copy link
Owner

df.sql(s) might be the intended, but users will probably first try writing df.query(s). but query is already used by pandas...

does that mean it makes sense to prefix with df.pqd.query?

@ajfriend
Copy link
Owner Author

ajfriend commented Sep 25, 2022

There's a risk that a query works "accidentally" without specifying the table/df correspondence because duckdb looks for dataframe names in scope. can we turn off this behavior?

# df.sql('select * from df where hour(ts_utc) = 8') # note!! this works because of duckdb defaults
df.sql('select * from tbl where hour(ts_utc) = 8', tbl=tbl2)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant