ValueError: Field 'id' expected a number but got 'Processing'

Question

I'm going to deploy my django application on DigitalOcean. Everything gone well, except following error, and my question is: where can I find source of this error, actually in which file?

Operations to perform:
  Apply all migrations: admin, auth, ccapp, contenttypes, sessions
Running migrations:
  Applying ccapp.0009_auto_20191207_2148...Traceback (most recent call last):
  File "/home/progbash/ccproject/env/lib/python3.6/site-packages/django/db/models/fields/__init__.py", line 1768, in get_prep_value
    return int(value)

ValueError: invalid literal for int() with base 10: 'Processing'

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "manage.py", line 21, in <module>
    main()
  File "manage.py", line 17, in main
    execute_from_command_line(sys.argv)
  File "/home/progbash/ccproject/env/lib/python3.6/site-packages/django/core/management/__init__.py", line 401, in execute_from_command_line
    utility.execute()
  File "/home/progbash/ccproject/env/lib/python3.6/site-packages/django/core/management/__init__.py", line 395, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
...
  File "/home/progbash/ccproject/env/lib/python3.6/site-packages/django/db/models/fields/__init__.py", line 2361, in get_db_prep_value
    value = self.get_prep_value(value)
  File "/home/progbash/ccproject/env/lib/python3.6/site-packages/django/db/models/fields/__init__.py", line 1772, in get_prep_value
    ) from e
ValueError: Field 'id' expected a number but got 'Processing'.

models.py:

from django.db import models
from datetime import datetime

class Question(models.Model):
    question_text = models.TextField(max_length=200)
    answer = models.TextField(max_length=200)

    def __str__(self):
        return self.question_text

class ApplicantStatus(models.Model):
    class Meta:
        verbose_name_plural = "Applicant Statuses"
        
    name = models.CharField(max_length=30)
    
    def __str__(self):
        return self.name

class Applicant(models.Model):
    name = models.CharField(max_length=20)
    surname = models.CharField(max_length=30)
    birth_date = models.DateField(blank=False)
    phone = models.CharField(max_length=15)
    email = models.EmailField(max_length=40)
    motivation_letter = models.TextField(max_length=200)
    status = models.ForeignKey(ApplicantStatus, on_delete=models.CASCADE, default=3)
    photo = models.FileField(upload_to='static/applicant_photos', blank=True)

    def __str__(self):
        return self.name

class Message(models.Model):
    message_text = models.CharField(max_length=200)
    sender_name = models.CharField(max_length=30)
    sender_email = models.EmailField(max_length=50)

    def __str__(self):
        return self.sender_name

You likely are filtering with something like `SomeModel.objects.filter(id=bla)`, with `bla` a variable that now contains `Processing`. Probably the error is located in the view that is triggering the error. — Willem Van Onsem, Dec 10 '19 at 11:55
Here is that part of my view: ```def index(request): context = { 'questions': Question.objects.all(), 'applicants': Applicant.objects.filter(status=1), 'empty_cards': range(4 - Applicant.objects.filter(status=1).count()) } ``` — srvqaqa, Dec 10 '19 at 11:56
is that the full traceback? i.e. is there anything else before the first `ValueError` line on the op? — buran, Dec 10 '19 at 11:57
Please post your migration file (the one in ccapp/migrations whose name startswith "0009_auto_20191207_2148"). That's where the root problem is. — bruno desthuilliers, Dec 10 '19 at 12:01
@Exprator we don't care about the models actually, the issue is in a migration. — bruno desthuilliers, Dec 10 '19 at 12:02

score 15 · Answer 1 · answered Oct 21 '20 at 03:26

Just to share the solution that worked with my similar error that been received: In my case, this same error was received because I was creating the model instant with the fields values directly, without specifying the field name, so always the ID was taking the first one as default (ID=field1). The problem solved by adding the attributes name as well to the Instant creation.

Was:

model_instant = YourModel(field1, field2,...etc)

Solved by:

model_instant = YourModel(field1 = field1, field2 = field2,...etc)

Do this then follow what been recommended above of 1) deleting the dB file, and 2) delete the migrations then 3) do the makemigrations your_app_name then 4) migrations, then 5) run the server and you should be good to go.

I faced same problem. It was solved by passing named arguments. — ABN, Mar 31 '21 at 23:04

score 9 · Answer 2 · answered Mar 29 '20 at 00:44

9

Just delete all the migration files except the init python file the run python manage.py makemigrations then python manage.py migrate

answered Mar 29 '20 at 00:44

Utibe

171
2
3

14

don't do this if you already have data in your database. – MikeSchem Oct 11 '21 at 23:39
8

This is not at all helpful to the question at hand without any context, please don't don't do the above – ekydfejj Feb 07 '22 at 08:20
it is not the actual solution – djangodeveloper Jun 25 '22 at 15:07

score 8 · Accepted Answer · answered Dec 10 '19 at 12:02

8

The problem was in migration files. I just opened and changed default value from string type to integer.

answered Dec 10 '19 at 12:02

srvqaqa

442
1
5
18

1

From which migration files did you make the change? – Gathide May 20 '20 at 05:31
I got **AttributeError: 'int' object has no attribute 'replace'** – AnonymousUser Nov 19 '21 at 04:20
I solved the problem when using `get_or_create`, make sure to add `created` like this `my_model, created = myModel.objects.get_or_create(someForeignKeyField=someModel)` – AnonymousUser Apr 26 '22 at 04:46

Yabesh · Answer 4 · 2021-10-25T13:44:35.923

6

From the migration files, we can find the file starting with (001_initial.py,002_auto.py,003_,004_). In those files replace the default value empty string (default= '') or django.utils.timezone.now() into integer like (default=1). It might solve the problem.

edited Oct 25 '21 at 13:44

answered Oct 25 '21 at 13:39

Yabesh

109
2
9

Please provide proper explanation like how above code would work – Tapan Hegde Oct 25 '21 at 15:35

AnonymousUser · Answer 5 · 2022-04-26T05:14:38.900

I got this error when I never added created to the get_or_create

someVariable = "someVariable"

# This will give the error "ValueError: Field 'id' expected a number but got someVariable"

my_model = myModel.objects.get_or_create(someField=someVariable)

It got solved when adding this

# added created

my_model, created = myModel.objects.get_or_create(someField=someVariable)

See this https://docs.djangoproject.com/en/4.0/ref/models/querysets/#get-or-create

score 1 · Answer 6 · answered Jul 22 '22 at 05:58

I was getting a similar error and finally found the cause. Just sharing here in case someone made a similar mistake.

I had defined a custom __init__ method on my model and had by mistake only written one * when passing kwargs to super:

def __init__(self, *args, **kwargs):
    super().init(*args, *kwargs)

This resulted in the error message:

ValueError: Field 'id' expected a number but got 'account'.

account was the first keyword argument I was passing when creating a new instance in a view. In hindsight, the error message makes sense, but it took me an hour of confused debugging before I noticed my typo.

It took me 2 days to realize the same, so kudos for you for solving it in just 1 hour! :) — Floella, Mar 10 '23 at 21:05

score 0 · Answer 7 · answered Jun 09 '20 at 08:49

I had the same problem with simple CBV like TemplateView or ListView which does not require mandatory parameter. I'm pretty sure the issue comes from the url interpretation. For a simple ListView like

class ProfileList(generic.ListView):
    model = get_user_model()

The url

path('profile_list/dummy', ProfileList.as_view(), name='profile_lv'),

works, whereas the one below, doesn't, the error: Field 'id' expected a number but got 'profile_lv' is thrown. Where profile_lv is the name of the url...

path('profile_list', ProfileList.as_view(), name='profile_lv'),

The addition of anything with a slash(/) after the path works?!...

score 0 · Answer 8 · answered Jul 22 '20 at 07:45

Just do nothing There are two ways : 1)Delete Your all migrations and type in your terminal:python3 manage.py makemigrations <app_name> then python3 manage.py migrate and then runserver.

2)Just opened and changed default value from string type to integer.

In my opinion choose first option because it is safe way.

Thanks

score 0 · Answer 9 · answered Dec 09 '20 at 08:25

0

Please Delete your recentally created migrations file then run python manage.py makemigrations and python manage.py migrate. I think your problem going to solve.Please try it now.

answered Dec 09 '20 at 08:25

Rahul Rai

9
2

score 0 · Answer 10 · answered Feb 06 '21 at 08:33

0

Go to migration files and find the name id is where generate, then just replace id with processor or other name or remove it as it define as verbose_name.

`python manage.py makemigrations`
`python manage.py migrate`
`python manage.py runserver`

answered Feb 06 '21 at 08:33

Parag Kulkarni

9
5

score 0 · Answer 11 · answered Jul 31 '21 at 06:05

0

Unfortunately, I was faced with this problem, but I was forced to create a new Django project from first, to solve this problem. And it was not solved by just deleting migrations files.

answered Jul 31 '21 at 06:05

Aylin Naebzadeh

125
2
9

score 0 · Answer 12 · answered Aug 30 '21 at 20:33

0

I have confronted with similar type of error. My original URL was this one:

v1/unit/

Cleaning the migration files didn't help me. Fortunately, It just started to work after extending the URL with an additional string:

v1/unit/addProduct/

answered Aug 30 '21 at 20:33

Zekarias Taye Hirpo

659
8
18

score 0 · Answer 13 · answered Aug 30 '22 at 01:15

You can do the following:

Clean up your dbase by deleting entries which do not confirm to your model, or putting in values for missing/wrong entries
Make sure values in models are blank=False, null=False and defaults given and then rerun the migration
Put a condition such as if Table.field != "": or whatever value is causing problem in your serializers

score 0 · Answer 14 · answered May 11 '23 at 15:48

I got the similar error below:

TypeError: Field 'id' expected a number but got <Country: USA>.

Because get_country() returns an object to default instead of id as shown below:

# "models.py"

class Country(models.Model):
    name = models.CharField(max_length=20)

    def __str__(self):
        return self.name

    @classmethod
    def get_country(cls): # ↓ ↓ ↓ An object is returned ↓ ↓ ↓
        return Country.objects.get_or_create(id=1, name="USA")[0]

class Shipping(models.Model):
    country = models.ForeignKey(
        Country, # ↓ An object is returned
        default=Country.get_country,
        on_delete=models.CASCADE
    )
    fee = models.DecimalField(max_digits=5, decimal_places=2)

    def __str__(self):
        return str(self.country)

So, I returned id from get_country() as shown below, then the error was solved:

# "models.py"

class Country(models.Model):
    name = models.CharField(max_length=20)

    def __str__(self):
        return self.name

    @classmethod
    def get_country(cls):                                       # ↓ Here
        return Country.objects.get_or_create(id=1, name="USA")[0].id

Be careful, even if changing self.name to str(self.id) as shown below:

# "models.py"

class Country(models.Model):
    name = models.CharField(max_length=20)

    def __str__(self):
        return str(self.id) # Here

    @classmethod
    def get_country(cls):
        return Country.objects.get_or_create(id=1, name="USA")[0]

# ...

Or, even if removing __str__() as shown below:

# "models.py"

class Country(models.Model):
    name = models.CharField(max_length=20)

    # def __str__(self):
    #     return str(self.id)

    @classmethod
    def get_country(cls):
        return Country.objects.get_or_create(id=1, name="USA")[0]

# ...

Then, the error was not solved.

score -3 · Answer 15 · answered Oct 20 '21 at 13:37

-3

I solved it by deleting the db, migrations and pycache files then run migrations & migrate again.

answered Oct 20 '21 at 13:37

mutabazigakuba

25
6

Your answer could be improved with additional supporting information. Please edit to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers in the help center. – Tapan Hegde Oct 20 '21 at 14:40

ValueError: Field 'id' expected a number but got 'Processing'

15 Answers15

Linked