Strange behavior with empty or None

[alexandre-fundcraft]

I've seen the problem, and I know how to solve the problem, it is just a question.
Is it normal return an instance with empty attributes Country(code=None) or Country(code='')?
I whould like to know the reason for this behavior if it is possible.
My approach is return None (I don't use empty strings)

Thanks

[SmileyChris]

Thanks for raising this! Your intuition was right - returning None for nullable fields makes more sense.

This is now fixed in #484 for the null=True case. Here's how it works now:

Field config	DB value	Returns
null=True	NULL	None ✨
blank=True	'' (empty string)	Country(code='')

The empty string behavior (Country(code='')) is kept intentionally to match Django conventions - blank=True stores empty form input as '' in the database, which is distinct from NULL (no value at all).

If you want None for "no country selected", use null=True, blank=True on your field. That way empty form submissions will store NULL and return None when accessed.