Django中无法访问主键：孵化器详情页跳转报错求助

Hey there! I totally get how frustrating it is when you’re sure you’re on the right track (using primary keys makes total sense here) but keep hitting errors. Even with your URLs sorted, there are a handful of common pitfalls in the models and views that could be tripping you up. Let’s break down the most likely culprits:

• Model-level misconfigurations

  • Double-check if your Incubator model uses a custom primary key instead of Django’s default id field. If you’ve set a field with primary_key=True (like incubator_uuid), you need to make sure your view is referencing that exact field instead of assuming pk maps to id.
  • Ensure all fields you’re trying to display in the detail view are actually defined in your Incubator model—typos like incubator_name vs name are super easy to miss.

• View logic mistakes

  • Did you use get_object_or_404 correctly? It should look something like incubator = get_object_or_404(Incubator, pk=pk)—if you swapped the model class or used the wrong parameter name (e.g., using incubator_id instead of pk when your URL uses <int:pk>), this will fail.
  • Don’t forget to pass the retrieved incubator object to your template context! If your render call doesn’t include something like {'incubator': incubator}, your template won’t have access to the data and will throw a variable not found error.
  • If you’re using a class-based view (like DetailView), make sure you’ve set the model attribute correctly and that the context_object_name matches what you’re using in the template.

• Template rendering issues

  • Verify your link to the detail page is passing the correct primary key. It should be something like {% url 'incubator_detail' incubator.pk %}—watch out for typos (e.g., incubators.pk instead of incubator.pk) or using the wrong field (like incubator.id when your model uses a custom PK).
  • Check that you’re referencing the right field names in your detail template. If your model has a description field but you wrote {{ incubator.desc }} in the template, you’ll get an empty value or an attribute error.

• Type mismatch problems

  • If your Incubator model uses a non-integer primary key (like a UUID or string), your URL path converter needs to match. For example, if you’re using UUIDs, your URL should use <uuid:pk> instead of <int:pk>—using the wrong converter will cause Django to look for an object with a mismatched ID type, resulting in a 404.

These are all super common "oops" moments that even experienced devs run into. Start by checking the simplest things first (like typos in field names or parameter names) and work your way through the list—chances are you’ll spot the issue quickly!

内容的提问来源于stack exchange，提问作者Arjun Kashyap