PK vs UUID - Conceptual ?

Using Django Getting Started
1

I am working on an app that will be used as a survey for clients to get their assessment of continuity planning. The first go to a landing page that collects first/last/email/company and then answer a series of questions and the results are tabulated a displayed.

Would requiring a password ensure someone can’t just go to teh survey pages without login in? Or is theree another way to stop that?

Is there any advantage to creating a UUID for each user vs using the PK created automatically?

If I chose to repopulate based on having previously answered I would just want to ensure the new data replaces the old and does not become a new row of answers.

2

Just requiring a password doesn’t prevent anything. You need to configure your views to ensure that users accessing them are authenticated. See Limiting access to logged-in users.

In theory, it makes it more difficult (if not impossible) to guess the PK of other users. Whether or not that’s a real issue is a different question. (I don’t agree, but that’s my opinion.)

3

Thanks, I’ll stick with PK