Django Admin中保存后NullBooleanField不显示None状态问题

I’ve run into this exact behavior before — it’s not exactly a "bug" but rather a quirk in how Django’s default NullBooleanSelect widget interacts with custom choices for NullBooleanField. The good news is there’s a straightforward fix.

The Root Cause #

When you use custom choices with NullBooleanField, the default NullBooleanSelect widget doesn’t properly map your custom "Unknown" label back to the None value after saving. Even though the database correctly stores NULL, the widget fails to recognize that None should correspond to your custom choice, so it appears unselected in the admin.

The Solution: Replace the Default Widget #

Instead of relying on NullBooleanSelect, use a standard Select widget paired with a ChoiceField in your admin form. This ensures your custom choices are properly mapped and the selected value persists after saving.

Here’s how to implement it:

1. Create a custom admin form for your model:

from django import forms
from django.contrib import admin
from .models import YourModel  # Replace with your actual model

class YourModelAdminForm(forms.ModelForm):
    # Reuse your custom choices here
    BOOL_CHOICES = [(True, 'Yes'), (False, 'No'), (None, "Unknown")]
    
    # Override the field to use ChoiceField and Select widget
    handicap_accessible = forms.ChoiceField(
        choices=BOOL_CHOICES,
        required=False,
        widget=forms.Select
    )

    class Meta:
        model = YourModel
        fields = '__all__'

2. Attach this form to your model admin:

class YourModelAdmin(admin.ModelAdmin):
    form = YourModelAdminForm

admin.site.register(YourModel, YourModelAdmin)

Why This Works #

By using ChoiceField and Select, you’re bypassing the default NullBooleanSelect widget’s internal logic that clashes with custom choices. The widget will now directly match the None value from the database to your "Unknown" choice, keeping it selected after save while still storing NULL correctly in the database.

If you prefer to stick closer to the original widget, you could also subclass NullBooleanSelect and override its options property to use your custom labels, but the above method is simpler and more reliable for most cases.

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