Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit 5eff875

Browse files
committed
chore: remove examples section
1 parent 30b1127 commit 5eff875

File tree

1 file changed

+0
-7
lines changed

1 file changed

+0
-7
lines changed

‎references/joins.mdx

Lines changed: 0 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -564,12 +564,6 @@ ORDER BY "orders_total_order_amount" DESC
564564
LIMIT 500
565565
```
566566

567-
**See examples in our demo:**
568-
- [Single one-to-many join example](https://demo.lightdash.cloud/...)
569-
- [Chained one-to-many joins example](https://demo.lightdash.cloud/...)
570-
- [Multiple one-to-many joins example](https://demo.lightdash.cloud/...)
571-
572-
573567
### Known limitations
574568

575569
There are a few situations where Lightdash doesn't currently handle inflated metrics:
@@ -643,4 +637,3 @@ In this case, each row represents a real charge, and the total billing (TechCorp
643637

644638
**How it works:** When fanout handling is enabled for your Lightdash organization, Lightdash warns you about joins that will likely create fanouts. To remove these warnings and enable fanout protection, specify the join relationship and primary keys in your model.yaml file (details [here](#handling-fanouts)).
645639
This keeps your setup clean and prevents inflated metrics.
646-

0 commit comments

Comments
(0)

AltStyle によって変換されたページ (->オリジナル) /