Add a faked column to django_migrations?

[KommuSoft]

Code of Conduct

• I agree to follow Django's Code of Conduct

Feature Description

Add a faked column to the Migration model.

Problem

Sometimes migrations got faked, it might however be useful to know this. Can we add a faked column to the migration model which is by default false, but does some bookmarking whether the migration was added to the table because it was migrated, or just faked?

Request or proposal

request

Additional Details

No response

Implementation Suggestions

No response

[github-actions]

Thank you KommuSoft for sharing your idea! We have a lot of them so please be patient. You can see the current queue here.

Community instructions

For commenters, please use the emoji reactions on the issue to express support, and/or concern easily. Please use the comments to ask questions or contribute knowledge about the idea. It is unhelpful to post comments of "I'd love this" or "What's the state of this?"

Reaction Guide

• 👍 This is something I would use
• 👎 This is something that would cause problems for me or Django
• 😕 I’m indifferent to this
• 🎉 This is an easy win

[RealOrangeOne]

which is by default false

How do you imagine backfilling the data? Adding a new column will mark all existing rows as the default value, despite it being impossible to know for existing rows.

Perhaps a nullable boolean? NULL could then represent an unknown state.

[KommuSoft]

@RealOrangeOne: we can also fill it with NULL to backpopulate, so:

        migrations.AddField(
            model_name='migration',
            name='faked',
            field=models.BooleanField(default=None, null=True),
            preserve_default=False,
        ),
        migrations.AlterField(
            model_name='migration',
            name='faked',
            field=models.Boolean(default=False, null=True),
        ),

the faked column is more informative. We could probably also use it in showmigrations to note faked migrations with [F] instead of [X].