SpacetimeAggregation.execute() throws unhelpful errors with sqlalchemy `engine`
Open
Nobody has claimed this yet.
collate
- Dominant language
- Jupyter Notebook
- Stars
- 201
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
From @mbauman on February 9, 2017 19:32
… instead of engine.connect(). The errors make it look like there's a problem within the quoting of SQL columns and schemas, which is really bizarre. It'd be nice if we could at a minimum assert that the connection is what we think it is.
Copied from original issue: dssg/collate#61
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at SpacetimeAggregation.execute and reproduce the failure by passing a SQLAlchemy engine instead of engine.connect(). Compare the resulting error with the misleading SQL quoting and schema errors; done means an incorrect connection input produces a clear, actionable error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, sqlalchemy
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100