Is it bad to use short (20 chars) random strings as primary keys?

• ksuid

  38 4,679 3.1 Go

  K-Sortable Globally Unique IDs

  

Try this instead. It's shorter than a UUID and without the dashes, so it seems to meet your requirements.

• ulid

  11 4,094 4.3 Go

  Universally Unique Lexicographically Sortable Identifier (ULID) in Go

  

I'm not concerned too much about the performance or the storage size at this stage. I've checked ulids before posting (more specifically https://github.com/oklog/ulid) but the only difference than a random string (especially if you use them with math.rand) is the timestamp prefix which makes them sortable, but I don't need that (users could use the internal SQLite rowid if they needed to sort by a primary key).

• WorkOS

  workos.com sponsored

  The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  

Suggest a related project