# setCompID clarification

**URL:** <https://odm.discourse.group/t/setcompid-clarification/205>\
**Category:** Uncategorized\
**Created:** [August 11, 2026, 4:41pm UTC](https://odm.discourse.group/t/setcompid-clarification/205 "2026-08-11T16:41:02Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![wastewater\_belgium](https://avatars.discourse-cdn.com/v4/letter/w/c0e974/32.png) [@wastewater\_belgium](https://odm.discourse.group/u/wastewater_belgium)\
**Post date:** [August 11, 2026, 4:41pm UTC](https://odm.discourse.group/t/setcompid-clarification/205/1 "2026-08-11T16:41:02Z")

</div>

Hi,

I have an extra question about setCompID in sets table. A composite key is a primary key taking into account two variables in a table. setCompID is not stricly speaking a composite key. It is the concatenation of setID and partID. Of course this concatenation should be unique.

I would mention setCompID as PK in the ERD.

 ![image](https://global.discourse-cdn.com/free1/uploads/odm/original/1X/15d5d6bb4be540864eb76db75bf6659964574d9b.jpeg)

---

<div class="post-metadata">

**Author:** ![matthomson](https://avatars.discourse-cdn.com/v4/letter/m/dec6dc/32.png) [@matthomson](https://odm.discourse.group/u/matthomson)\
**Post date:** [August 14, 2026, 5:37pm UTC](https://odm.discourse.group/t/setcompid-clarification/205/2 "2026-08-14T17:37:44Z")

</div>

Fair enough - thank you for the flag! I’ve made the adjustment in the 3.0.1 release draft and it should be PK moving forward. Thank you again!

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/free1/uploads/odm/original/1X/34f6410d4262a308493f8c3b977a49666a3a2929.png) [@system](https://odm.discourse.group/u/system)\
**Post date:** [August 17, 2026, 8:44am UTC](https://odm.discourse.group/t/setcompid-clarification/205/3 "2026-08-17T08:44:10Z")

</div>

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.