Help with compound key

[porsche (porscheme)]

• In PersonalDetail type, can I define compound key(index) on codeId & timestamp fields?

  type Tcode {
    codeConceptId: Int! @id
    domain: String!
  }
  
  type PersonalDetail {
    codeId: Tcode!
    hasEthnicityId: Tcode!
    hasGenderId: Tcode!
    hasMaritalStatusId: Tcode!
    hasRaceIds: [Tcode]!
    timestamp: Int! @search
  }
  

[jdgamble555 (Jonathan Gamble)]

You are asking two questions, so I am going to answer the one from the title. Please edit this post, delete the second question, and create a new post for that question.

Support for composite primary keys

I think the ideal case would be having both your @id middleware which seems an amazing idea to describe composite ids, and @unique to ensure uniqueness for certain fields and being able to filter by those, so something like this could be intuitive and powerful: type Application @id(person, job) { id: ID! person: Person! job: Job! applicationCode: String! @Unique ... } And yes! I wish pre-hooks are a thing soon!

There are dozens of posts on composite (compound keys) which don’t exist in DGraph, but there are potential work arounds depending on your use case. The thread above should help get you started through the Discuss rabbit hole.

J