Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update README.md to reflect changes inReferenceAttribute #89

Merged
merged 1 commit into from
Mar 1, 2024
Merged

Update README.md to reflect changes inReferenceAttribute #89

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -297,7 +297,7 @@ If desired, this can be avoided by making specific join models that do not have

**By default** relations expect to be used as top level filters on a query. If following the models above, this would
mean that a `Movie` with no `Person` relations on it would not return on a query **unless** the `Relation`
has `shouldFilterTopLevel` set to `false`:
has `useInnerJoin` set to `false`:

The following model would return any movie, even if there are no `Person` models associated with it:

Expand All @@ -311,7 +311,7 @@ public class Movie : BaseModel
[Column("name")]
public string? Name { get; set; }

[Reference(typeof(Person), shouldFilterTopLevel: false)]
[Reference(typeof(Person), useInnerJoin: false)]
public List<Person> People { get; set; } = new();
}
```
Expand Down
Loading