Missing model after squashing

[Sebastian Jekutsch]

Sorry for an unspecific subject and not searching for duplicates due to lack of knowledge, understanding and time.

As an excerpt from #34924 which has been correctly closed as duplicate for two of its issues, the third one remains unresolved, as far as I see. I reopen it with this new report.

Based on the attachments

1. Zip of single migrations 0001 to 0116
2. Resulting squashed migration file of "manage.py squashmigrations knowledgebase 0116"
3. models.py at the end of 0116

within #34924,
I found that model Activity has errorneously disappeared completely in the squashed migration file. It has even not been detected by a new makemigrations run for cross-check.

[Mariusz Felisiak]

Activity is in the squashed migration.

[Sebastian Jekutsch]

Right, but it's below its first reference in model Topic within the script, so an initial database migration will raise an "ValueError: Related model 'knowledgebase.activity' cannot be resolved".
(Apologize for not stating the problem more specific.)

[Mariusz Felisiak]

Replying to Sebastian Jekutsch:

Right, but it's below its first reference in model Topic within the script, so an initial database migration will raise an "ValueError: Related model 'knowledgebase.activity' cannot be resolved".
(Apologize for not stating the problem more specific.)

That is also not true:

        migrations.CreateModel(
            name="Activity",
            fields=[
                (
                    "id",
                    models.BigAutoField(
                        auto_created=True,
                        primary_key=True,
                        serialize=False,
                        verbose_name="ID",
                    ),
                ),
                ("name", models.CharField(max_length=50)),
                (
                    "members",
                    models.ManyToManyField(
                        blank=True,
                        related_name="memberships",
                        to="knowledgebase.activity",
                    ),
                ),
                ("alternative_names", models.CharField(blank=True, max_length=250)),
            ],
            options={
                "verbose_name": "Activity",
                "verbose_name_plural": "Activities",
                "ordering": [django.db.models.functions.text.Lower("name")],
            },
        ),
        migrations.AddField(
            model_name="topic",
            name="activities",
            field=models.ManyToManyField(
                blank=True, related_name="activities", to="knowledgebase.activity"
            ),
        ),

Please see TicketClosingReasons/UseSupportChannels for ways to get help and don't use Trac as a support channel.

[Sebastian Jekutsch]

Ok, seems I have differences locally.