Skip to content

Commit a5becb7

Browse files
authored
Removed link to deleted Notion page
1 parent 47152ba commit a5becb7

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

content/en/engines/mergetree-table-engine-family/versioned-collapsing-mergetree.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -607,7 +607,7 @@ select 'step2',* from Example5 final ;
607607

608608
### Complex Primary Key
609609

610-
I used a simple, compact column with Int64 type for the primary key in previous examples. It's better to go this route with monotonically growing IDs like autoincrement ID or [SnowFlakeId](https://www.notion.so/4a5c621b1e224c96b44210da5ce9c601?pvs=21) (based on timestamp). However, in some cases, a more complex primary key is needed. For instance, when storing data for multiple tenants (Customers, partners, etc.) in the same table. This is not a problem for the suggested technique - use all the necessary columns in all filters and JOIN operations as Tuple.
610+
I used a simple, compact column with Int64 type for the primary key in previous examples. It's better to go this route with monotonically growing IDs like autoincrement ID or SnowFlakeId (based on timestamp). However, in some cases, a more complex primary key is needed. For instance, when storing data for multiple tenants (Customers, partners, etc.) in the same table. This is not a problem for the suggested technique - use all the necessary columns in all filters and JOIN operations as Tuple.
611611

612612
```sql
613613
create table Example6

0 commit comments

Comments
 (0)