[weird-eye-issue]

That sounds really overkill for simply wanting an identifier that doesn't change, isn't guessable, and doesn't reveal how many rows there are

[staticassertion]

We'll have to agree to disagree. Systems like the ones I described are a hell of a lot easier to build on long term while maintaining those invariants.

[weird-eye-issue]

How is that easier to maintain than literally just having a UUID primary key? I feel like we must be talking about different use cases

[staticassertion]

If your goal is to use the uuid as a delegated capability it's going to be much more complex to use the primary key for your row than to use a separate key.

[weird-eye-issue]

Yeah we are talking about different use cases entirely