loopbackio / loopbackio/loopback-connector-oracle
Multiple foreignkeys possibility in Model Relation?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 28
- Forks
- 32
- PR merge metrics
- No merged PRs in 30d
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 on loopback-connector-postgres
https://github.com/strongloop/loopback-connector-postgresql/issues/184
I am in the same situation on Oracle 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 reviewing the linked LoopBack, MySQL, and PostgreSQL issues, then inspect how this Oracle connector currently handles model relations. Define what support for a model definition using foreignKey ["id1", "id2"] should mean and document tests or examples needed to show that composite foreign keys work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100