Skip to content

Commit 857529b

Browse files
authored
Update data-graph.md
1 parent 1b01ac6 commit 857529b

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

src/unify/data-graph/data-graph.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -150,7 +150,7 @@ Now define your relationships across your entities. The Data Graph supports thre
150150

151151
All relationship types require you to define the relationship slug, label, and related entity. Each type of relationship has unique join on conditions.
152152

153-
#### Relationship #1: Define profile-to-entity relationship
153+
#### Define profile-to-entity relationship
154154
This is the first level of relationships and a unique type of relationship between Segment profile entity and a related entity.
155155

156156
| Parameters | Definition |
@@ -206,7 +206,7 @@ data_graph {
206206
}
207207
```
208208

209-
#### Relationship #2: Define a 1:many relationship
209+
#### Define a 1:many relationship
210210
For 1:many relationships, define the join on between the two entity tables using the spec below.
211211

212212
| Parameters | Definition |
@@ -247,7 +247,7 @@ data_graph {
247247
}
248248
```
249249

250-
#### Relationship #3: Define many:many relationship
250+
#### Define many:many relationship
251251
For many:many relationships, define the join on between the two entity tables with the `junction_table`.
252252

253253
> warning ""
@@ -262,10 +262,10 @@ For many:many relationships, define the join on between the two entity tables wi
262262
**Junction table spec**
263263
| Parameters | Definition |
264264
| ----------- | --------------------------------------------------------------------- |
265-
| `table_ref` | Defines the fully qualified table reference to the join table.: `[database name].[schema name].[table name]` Segment flexibly supports tables, views and materialized views |
265+
| `table_ref` | Defines the fully qualified table reference to the join table: `[database name].[schema name].[table name]` Segment flexibly supports tables, views and materialized views |
266266
| `primary_key` | The unique identifier for the given table. Must be a column with unique values per row |
267-
| `left_join_on` | Define the relationship between the left entity table and the junction table: `[left entity slug].[column name] = [junction table column name]`. `[schema].[table]` is implied within the junction table column name, so you do not need to define it again |
268-
| `right_join_on` | Define the relationship between the junction table and the right entity table: `[junction table column name] = [right entity slug].[column name]`.`[schema].[table]` is implied within the junction table column name, so you do not need to define it again |
267+
| `left_join_on` | Define the relationship between the left entity table and the junction table: `[left entity slug].[column name] = [junction table column name]`. Note that schema and table are implied within the junction table column name, so you do not need to define it again |
268+
| `right_join_on` | Define the relationship between the junction table and the right entity table: `[junction table column name] = [right entity slug].[column name]`. Note that schema and table are implied within the junction table column name, so you do not need to define it again |
269269

270270
**Example:**
271271

0 commit comments

Comments
 (0)