INCATools / INCATools/semantic-sql
Add a duckdb export or convert base layer to duckdb
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 69
- Forks
- 7
- Avg merge
- 8m
- Merged PRs (30d)
- 1
Description
Duckdb has a lot of advantages over sqlite
- speed
- extended syntax
- built in support for arrays and other datatypes
In theory there is no particular reason for a duckdb export. You can just point duckdb at any of the semsql builds and it works. But there are some oddities that occur and it would be better to have a dedicated duckdb export
This could be a simple mirror of the sqlite. However, there is the opportunity to take advantage of increased expressivity. For example, we could have tables like
```
CREATE TABLE term_info (
id VARCHAR,
label VARCHAR,
aliases VARCHAR[],
....
)
```
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 by examining the existing SQLite export and the semsql builds to understand the current schema and the oddities described. Decide whether the work should provide a dedicated DuckDB export or convert the base layer, then verify that the resulting tables support the proposed DuckDB-oriented types and remain usable by DuckDB.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sql, sqlite
- Domain
- database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100