Custom primary key allows to record a null or blank value

This is not a bug, since an empty string is a valid primary key value (just not a particularly useful one). Please post something to the django-users list if you need more help with this, but using "blank=False" will probably solve your problem.

Replying to mtredinnick:

This is not a bug, since an empty string is a valid primary key value (just not a particularly useful one). Please post something to the django-users list if you need more help with this, but using "blank=False" will probably solve your problem.

I agree with you about that an empty string can be used as primary key, but in the django model reference you can read this: primary_key

If True, this field is the primary key for the model.

If you don't specify primary_key=True for any fields in your model, Django will automatically add this field:

id = models.AutoField('ID', primary_key=True)

Thus, you don't need to set primary_key=True on any of your fields unless you want to override the default primary-key behavior.

primary_key=True implies blank=False, null=False and unique=True. Only one primary key is allowed on an object.

I believe that if setting primary_key to True, implies the previous mentioned statements, then would be not possible to create a blank string primary key.

If I'm wrong, please, explain me what's my misunderstanding.

Thanks for the response.

revil is right: http://www.djangoproject.com/documentation/model_api/#primary-key. Either the behaviour of primary_key=True needs to change, or the docs.

This is a serious problem. Is there anything we can do to at least trick the problem?

I'm also running into this problem.

What would happen, if we change:

paramsis_required? = not self.blank and not self.primary_key and not rel

to

paramsis_required? = not self.blank and not rel

here? --> http://code.djangoproject.com/browser/django/trunk/django/db/models/fields/__init__.py#L300

(In [7713]) Fixed #3774 - primary_key=True does not, in fact, imply blank=False