loopbackio / loopbackio/loopback-connector-postgresql
Multiple foreignkeys possibility in Model Relation?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 118
- Forks
- 184
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 5
Description
This is issue already asked on core loopback tree:
https://github.com/strongloop/loopback/issues/2080
on loopback-connector-mysql tree:
https://github.com/strongloop/loopback-connector-mysql/issues/150
and loopback-connector-oracle:
https://github.com/strongloop/loopback-connector-oracle/issues/87
I am in the same situation on Postgres database.
So basically achieve following in model definition:
"foreignKey":["id1","id2"]
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 reading the linked LoopBack, MySQL connector, and Oracle connector issues, then inspect how relations and model definitions are handled in this PostgreSQL connector. Determine the expected behavior for a model definition using foreignKey as an array, and define completion around documented, tested support for multiple foreign keys.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js, postgresql
- Domain
- database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100