stale[bot]
commented
3 years ago This issue has been marked stale because it has not seen activity within six months. If you believe this to be in error, please contact one of the code owners, listed in the CODEOWNERS file at the top-level of this repository. This issue will be closed within 30 days of being stale.
Create a new section (or even a new page) in our docs for relations and explain users what relation type to choose depending on which database they use.·
We should verify that our recommended solution is actually a good one that works well for the target database. This will most likely require research on our side, as we don't have deep knowledge of different NoSQL databases. Such research is out of scope of this story, there will be follow-up spike stories. While creating the first version of the guide, we should simply label the entries that we are not confident about.
An example for illustration:
SQL databases
MongoDB
The suggestions above are an initial proposal. See the spike story #2342 for discussion about which LoopBack relations work best for MongoDB.
Cloudant & CouchDB
The suggestions above are an initial proposal. See the spike story #2343 for discussion about which LoopBack relations work best for MongoDB.
(etc. for other databases that have an LoopBack official connector)
See the discussion in #2127 to better understand the wider context and also #2340 for related work.
Acceptance criteria
For each of the following connectors, add a subsection explaining how to map 1-N/N-1/1-1 relation to LoopBack relation types. Each subsection should be started by a heading (level 3?) so that TOC is created at the top of the page and URLs can be created to point directly to each database name.