Opened 21 months ago

Closed 21 months ago

Last modified 21 months ago

#34253 closed Bug (invalid)

migrations don't apply — at Version 2

Reported by: Oleg Korsak Owned by: nobody
Component: Uncategorized Version: 4.1
Severity: Normal Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description (last modified by Oleg Korsak) 

# Generated by Django 4.1.5 on 2023-01-12 01:57

from django.db import migrations, models


class Migration(migrations.Migration):

    dependencies = [
        ('myApp', '0001_initial'),
    ]

    operations = [
        migrations.AlterField(
            model_name='report49',
            name='d29',
            field=models.IntegerField(default=1),
        ),
    ]

there is no such migration applied yet, but sqlmigrate shows:

BEGIN;
--
-- Alter field d29 on report49
--
-- (no-op)
COMMIT;

Initial migration didn't set any defaults as well

Change History (2)

comment:1 by Tim Graham, 21 months ago

Component: Uncategorized → Migrations
Resolution: → invalid
Status: new → closed

You haven't stated what the unexpected behavior is. If the migration doesn't execute any SQL (which is impossible to know given the information you provided) then the output looks correct. For example, if you added default=1 to the field, then no SQL queries are expected.

comment:2 by Oleg Korsak, 21 months ago

Component: Migrations → Uncategorized
Description: modified (diff)
Note: See TracTickets for help on using tickets.
Back to Top