Admin incompatible with non-integer primary keys

[Aymeric Augustin]

Since the admin log uses a GFK with an integer object_id, creating, modifying or deleting an object with a non-integer primary key fails.

For instance, it's impossible to edit the following model in the admin:

from django.db import models

class Release(models.Model):
    version = models.CharField(max_length=16, primary_key=True)

[Aymeric Augustin]

As a workaround, one can disable logging by adding these lines to the ModelAdmin class:

def log_addition(self, request, object): pass
def log_change(self, request, object): pass
def log_deletion(self, request, object): pass

[lakshman@…]

I just tested this on the development version and it seems to work fine.

[Aymeric Augustin]

Have you tested with a database that enforces types, ie. not SQLite?

On SQLite Django happily saves a string in an integer field and the bug doesn't appear.

[Aymeric Augustin]

#20088 reported this problem with a custom user model.

[Claude Paroz]

I don't doubt there are issues with non-integer PKs, but we still miss failure data. LogEntry.object_id is a TextField, so this is not the culprit. And I could add and delete an object with a non-integer primary key with Postgres.

[Claude Paroz]

The issue might be rather #20088 (which is now fixed).