Inconsistent data type for BigIntegerField after calling full_clean()

[anonymous]

Example:

class MyModel(Model):
    big = BigIntegerField()

    def full_clean(self):
        print type(self.big)
        super(MyModel, self).full_clean()
        print type(self.big)

When saving the model I get:

<type 'long'>
<type 'int'>

This means that full_clean() somehow converts the long to int. On the other hand, when getting the model from the database (MySQL in my case), the output of type(my_model.big) will be long again. From a user point of view this behavior is inconsistent and confusing.

[anonymous]

Also applies to Django 1.4

[Claude Paroz]

Could you provide a use case where this behaviour might lead to a bug?

[anonymous]

Use case: In my particular environment we have to check for data types in a custom clean() method in every model. Example code:

my_m = MyModel()
my_m.big = 2L
my_m.save()

my_m2 = MyModel()
my_m2.big = my_m.big
my_m2.save() #raises ValidationError, because an integer was provided

On the other hand tis code works without a validation error:

my_m = MyModel.objects.get(id=1)
my_m2 = MyModel()
my_m2.big = my_m.big
my_m2.save()

[Adam Duren]

Fixed and tests written, pull request ​https://github.com/django/django/pull/810

[Claude Paroz]

The patch doesn't account for Python 3 (where long type doesn't exist).

[Adam Duren]

I made the changes in pull request ​​https://github.com/django/django/pull/2202 as requested in pull request ​​https://github.com/django/django/pull/810.

[Areski Belaid]

This is already fixed on master, do we want to fix it on 1.4 or simply mark this ticket as wontfix?

[Tim Graham]

Per our ​supported versions policy, 1.4 is only receiving security fixes so we can close this. Thank-you for triaging.