1602 / 1602/jugglingdb

Composite primary keys / composite foreign keys

Offen
#465 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
Vorherrschende Sprache
JavaScript
Sterne
2k
Forks
238
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

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.

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
javascript, mongodb, mysql, nodejs, postgresql, redis, sqlite
Bereich
backend-api-design, databases
Issue-Typ
Feature
Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Aktivitätsstatus
Veraltet
Klarheit
Klar beschrieben
Anfängerfreundlichkeit
10/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.