Skip to content

Commit

Permalink
Merge ba7fa22 into 0ea29d8
Browse files Browse the repository at this point in the history
  • Loading branch information
achrinza committed Jan 17, 2020
2 parents 0ea29d8 + ba7fa22 commit fa0cd6f
Show file tree
Hide file tree
Showing 4 changed files with 29 additions and 0 deletions.
2 changes: 2 additions & 0 deletions docs/site/BelongsTo-relation.md
Expand Up @@ -6,6 +6,8 @@ sidebar: lb4_sidebar
permalink: /doc/en/lb4/BelongsTo-relation.html
---

{% include note.html content="There are certain limitations to `inclusionResolver()`. See [Limitations](Relations#limitations)." %}

## Overview

{% include note.html content="
Expand Down
2 changes: 2 additions & 0 deletions docs/site/HasMany-relation.md
Expand Up @@ -15,6 +15,8 @@ Using this relation with NoSQL databases will result in unexpected behavior,
such as the ability to create a relation with a model that does not exist. We are [working on a solution](https://github.com/strongloop/loopback-next/issues/2341) to better handle this. It is fine to use this relation with NoSQL databases for purposes such as navigating related models, where the referential integrity is not critical.
" %}

{% include note.html content="There are certain limitations to `inclusionResolver()`. See [Limitations](Relations#limitations)." %}

A `hasMany` relation denotes a one-to-many connection of a model to another
model through referential integrity. The referential integrity is enforced by a
foreign key constraint on the target model which usually references a primary
Expand Down
23 changes: 23 additions & 0 deletions docs/site/Relations.md
Expand Up @@ -6,6 +6,8 @@ sidebar: lb4_sidebar
permalink: /doc/en/lb4/Relations.html
---

{% include note.html content="There are certain limitations to `inclusionResolver()`. See [Limitations](Relations#limitations)." %}

## Overview

Individual models are easy to understand and work with. But in reality, models
Expand Down Expand Up @@ -56,3 +58,24 @@ application.

To generate a `HasMany` or `BelongsTo` relation through the CLI, see
[Relation generator](Relation-generator.md).

## Limitations

### Navigational properties

Navigational properties of related models cannot be created, updated, saved,
deleted or replaced, via the parent model. See its
[GitHub pull request](https://github.com/strongloop/loopback-next/pull/4148).

### Creating a model alongside its related models

Creating related models must be created separately after the parent model is
created. See its
[GitHub issue](https://github.com/strongloop/loopback-next/issues/4435).

### Filtering by parent model

[Where filters](https://loopback.io/doc/en/lb3/Where-filter.html) such as those
used by model queries (`create()`, `find()`, `replaceById()`, etc.) cannot be
used to filter a model by the value of its parent model. See its
[GitHub issue](https://github.com/strongloop/loopback-next/issues/4299).
2 changes: 2 additions & 0 deletions docs/site/hasOne-relation.md
Expand Up @@ -6,6 +6,8 @@ sidebar: lb4_sidebar
permalink: /doc/en/lb4/hasOne-relation.html
---

{% include note.html content="There are certain limitations to `inclusionResolver()`. See [Limitations](Relations#limitations)." %}

## Overview

{% include note.html content="
Expand Down

0 comments on commit fa0cd6f

Please sign in to comment.