Re: Django 3.2rc1: models.W042 is raised on inherited manually specified primary key.

Hi Caram, Django doesn't perform any DDL operations outside of migrations. You've probably set DEFAULT_AUTO_FIELD to BigAutoField, then you generated and run the migrations which caused some failures. We can check migration failures if you can provide a small project to reproduce. Best, Ma

Re: Django 3.2rc1: models.W042 is raised on inherited manually specified primary key.

I'm now discovering that some INT keys were subrepticely converting to BIGINT in the database without me noticing. And there is no BigAutoField in any of the migrations. More worrying, there seem to have been several other unwanted changes: 1. NOT NULL changed to DEFAULT NULL (or the other way r

Re: Django 3.2rc1: models.W042 is raised on inherited manually specified primary key.

Can you provide a small project to reproduce? Best, Mariusz -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-develo

Re: Django 3.2rc1: models.W042 is raised on inherited manually specified primary key.

My bad, I should have read the documentation more thoroughly before. However, when I set DEFAULT_AUTO_FIELD to BigAutoField and run the migration, I get errors like the following. This was what troubled me in the first place: django.db.utils.IntegrityError: (1452, 'Cannot add or update a child ro

Re: Django 3.2rc1: models.W042 is raised on inherited manually specified primary key.

Caram, I don't see any issue here. As far as I'm aware you're using the auto-created primary key. If you want to get rid of warnings and avoid unwanted migrations in the future, set DEFAULT_AUTO_FIELD to AutoF

Re: Django 3.2rc1: models.W042 is raised on inherited manually specified primary key.

Sorry, I meant to do that. Here's the link to the ticket: https://code.djangoproject.com/ticket/32367 I get an output similar to that of the ticket when I run `./manage makemigrations`: HINT: Configure the DEFAULT_AUTO_FIELD setting or the AppConfig.default_auto_field attribute to p

Re: Django 3.2rc1: models.W042 is raised on inherited manually specified primary key.

Hi, It would be helpful to link to the ticket and/or explain the issue in more detail. On Thursday, March 25, 2021 at 9:28:09 AM UTC-4 Caram wrote: > > This issue was raised in alpha1, but I still had the issue in beta1 and > now also in rc1. > > As a result, I have to manually edit the migrati

Django 3.2rc1: models.W042 is raised on inherited manually specified primary key.

This issue was raised in alpha1, but I still had the issue in beta1 and now also in rc1. As a result, I have to manually edit the migrations files and remove lines that alter fields to become BigField(). Has this really been fixed? Am I missing something obvious? Caram -- You received this