astrodbtoolkit / astrodbtoolkit/AstrodbKit
Consider use of Astropy QTable
- Dominant language
- Python
- Stars
- 12
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Astropy QTables are Tables with units enforced in them. The databases I have worked with thus far don't have units stored in them, but it may be that some will (perhaps if the data is in long-form) or that it can be added via some map.
We may want to consider adding a `.qtable` method that will return query output but do so in QTable form. The simplest implementation would probably require the user to provide a dictionary of column -> unit, but we can explore other options too.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the query-output API and reviewing how returned rows or tables are currently represented. Read the Astropy QTable requirements and compare them with the proposed `.qtable` method and column-to-unit dictionary. Done means the project has a decided unit-mapping approach and query results can be returned as QTables.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, sqlalchemy
- Domain
- backend-api-design, database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100