Investigate using DuckDB instead of `read_sql_query`

Open
#55 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
python, sql

Research direction

No file, test, or entry point is named. Start by locating the use of read_sql_query, then read the linked DuckDB article and compare the relevant APIs and performance. Done should include a documented investigation and a clear basis for deciding whether replacement is practical.

Written by the indexing model from the issue text.

Description

enhancement

We may be able to achieve significant performance boosts by replacing read_sql_query with DuckDB's API. For more info, refer here: https://duckdb.org/2021/05/14/sql-on-pandas.html

Dominant language
Python
Stars
10
Forks
0
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from alteryx/featuretools_sql

All issues in alteryx/featuretools_sql

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.