PhoneNumberField set to null=False and blank=True doesn't allow empty string

[anonymous]

I had model that used PhoneNumberField and it was optional, so set it to blank=True. I was dumping data and loading data using load data. When I did it complained because the field had "", which it said that the field couldn't be null. The CharFields didn't have the same issue. The only way I could load the data was to set the field equal to null. This is a bug, because null and empty are different even if it's a phone number.

[Malcolm Tredinnick]

This is a mess. The root problem here is that PhoneNumberField inherits from IntegerField in django/db/models/fields/__init__.py, but everywhere else it is treated as text: in its validator and in the database column we create (varchar(20))! Integer fields cannot have empty values, so we convert them to NULLs, leading to the problem noticed by the reporter.

I suspect the solution is to change the parent of PhoneNumberField and make sure the validation checks for all digits. However there may be unintended side-effects and backwards-incompatibilities there, so it needs checking.

[John DeRosa]

I've held on to this for too long. Other things keep getting in the way of working on this. So I'm releasing it back into the nobody ticket pool.

[curtis]

Change PhoneNumber from Int to Char field

[Chris Beaven]

Seems like this was fixed somewhere along the line -- PhoneNumberField in django.contrib.localflavor.us.models subclasses Field.