1602 / 1602/jugglingdb

Composite primary keys / composite foreign keys

Open
#465 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
2k
Forks
238
PR merge metrics
No merged PRs in 30d

Description

This does not seem to be mentioned in the documentation, and a quick Google search only points to an [unanswered Stack Overflow question from 2014](https://stackoverflow.com/questions/27222706/how-can-i-have-composite-primary-key-schema-in-jugglingdb).

The question is: does JugglingDB support composite keys, both for PKs and for relations?

I'm making that question because we will have to connect to FB dialect 1 databases from a legacy system; in fact, the new system is meant to run alongside it, so, any major database refactorings are out of question.

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue asks about composite primary and foreign key support across multiple database adapters. Start by examining the schema definition logic in lib/schema.js and the adapter interfaces for each database (e.g., lib/adapters). Look for existing key handling and relation definitions. 'Done' means implementing and testing composite key support for at least one adapter, ensuring it works with relations.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, mongodb, mysql, nodejs, postgresql, redis, sqlite
Domain
backend-api-design, databases
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
10/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.