Why 2 IDs (id and sid) are required?

[TokugawaTakeshi]

Here is the general definition of Session Prisma model from the README.md:

model Session {
  id        String   @id
  sid       String   @unique
  data      String   @db.MediumText  // MediumText may be needed for MySql
  expiresAt   DateTime
}

As far as I experimentally knew dbRecordIdIsSessionId option does not merge the id and sid to single column, it just fills the id and sid columns with the same value. Why it is impossible to use only 1 column? From the viewpoint of Prisma, the following model definition is correct (the sid will be used as primary key).

model Session {
  sid        String   @id
  data      String   @db.MediumText  // MediumText may be needed for MySql
  expiresAt   DateTime
}

Alternatively, the id can be used as the session ID:

model Session {
  id        String   @id // use as `sid`
  data      String   @db.MediumText  // MediumText may be needed for MySql
  expiresAt   DateTime
}

[kleydon]

Good point. Some users have wanted the ability for sid to be distinct / different from id - but I think you're right; it isn't necessary (from the Prisma/DB standpoint) for these to be different, and there could be a configuration option for there to be just one id.

[TokugawaTakeshi]

Thank you for the checking of this discussion.
Hope the API will be updated in the future.

[kleydon]

Thanks for pointing out the issue!
I'm pretty limited on time right now, but feel free to post a PR if you feel like it, and hopefully I (or others who rely on this library) can review the improvement.

[kleydon]

There is the boolean option: dbRecordIdIsSessionId, which causes the session id and record id to be identical. (This still uses the same db schema however, with separate fields for session and record ids.)