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

Add a duckdb export or convert base layer to duckdb #82

Open
cmungall opened this issue Apr 26, 2024 · 0 comments
Open

Add a duckdb export or convert base layer to duckdb #82

cmungall opened this issue Apr 26, 2024 · 0 comments

Comments

@cmungall
Copy link
Collaborator

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[],
   ....
)
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