Add tabbed examples for multiple node IDs #2512
Conversation
|
This PR includes documentation updates Updated pages: |
| @@ -1464,39 +1464,64 @@ Now use the previously defined ID spaces when connecting the actors to movies. | |||
| == Using multiple node IDs | |||
|
|
|||
| A node header can contain multiple `ID` columns. | |||
| The relationship data must then use a matching number of `START_ID` / `END_ID` columns as references to the composite value of those ID columns. | |||
|
|
|||
| Starting from 2025.07, the relationship data must then use a matching number of `START_ID` / `END_ID` columns as references to the composite value of those ID columns. | |||
There was a problem hiding this comment.
Is this true? If I read the comments for the https://github.com/neo-technology/neo4j/pull/31617 correctly, it is still allowed to use a single :START_ID/:END_ID to refer to a composite ID.
But it is not allowed to mix how to refer to composite IDs. Either all references must use a single :START_ID/:END_ID columns, or a matching amount.
I think this should be reflected on this page too.
| + | ||
| [.tabbed-example] | ||
| ===== | ||
| [role=include-with-multiple-node-IDs] |
There was a problem hiding this comment.
I don't like these headings. It was a super quick decision.
In fact, the first tab is on how to use a single :START_ID/:END_ID column, and the second one is for matching number of those columns.
Suggestions:
The first tab -- Using single ID column for composite IDs
The second tab -- Using multiple ID columns for composite IDs
| [role=include-with-multiple-ID-columns label--new-2025.07] | ||
| ====== | ||
|
|
||
| Starting from 2025.07, you have to use a matching number of `START_ID` / `END_ID` columns when defining the relationship: |
There was a problem hiding this comment.
| Starting from 2025.07, you have to use a matching number of `START_ID` / `END_ID` columns when defining the relationship: | |
| Starting from 2025.07, you can use a matching number of `START_ID` / `END_ID` columns when defining the relationship. | |
| However, do not mix how to refer to composite IDs. | |
| Either all references must use a single `START_ID` / `END_ID` column or a matching number of them. |
No description provided.