DuckDB? 🐤

Open
#140 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
15/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
postgres
Domain
databases

Research direction

Start by reading the linked DuckDB website and repository, then review how this project currently deploys and uses Postgres. The issue records an open question about deployment but names no files, tests, implementation target, or completion condition.

Written by the indexing model from the issue text.

Description

discuss enhancement T5m technical

A friend has recommended looking at DuckDB:
https://duckdb.org -> https://github.com/duckdb/duckdb

image

We don't _currently _have a use case for DuckDB as Postgres meets our needs just fine.
We aren't doing "big data" or analytics that require hyper fast queries.
Buuuuut ... opening this issue to capture. 📂

My biggest open question regarding DuckDB is deployment ... 🤷‍♂️ ❓

Dominant language
JavaScript
Stars
291
Forks
25
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 dwyl/technology-stack

All issues in dwyl/technology-stack

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.