Changes between Initial Version and Version 1 of Ticket #33673


Ignore:
Timestamp:
Apr 30, 2022, 1:50:49 PM (3 years ago)
Author:
George
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #33673 – Description

    initial v1  
    55Creating the migrations for this schema:
    66
    7 ```
     7
     8{{{
    89class M():
    910    a = models.IntegerField(default=1)
     
    1516            )
    1617        ]
    17 ```
     18}}}
     19
    1820
    1921Create the constraint `uniq_ab_1` is Postgres as expected (when using the `\d+` command on the table to visualize)
    2022
    2123However, this manual migration will remove the constraint, due to one of its member columns being deleted, this is just standard Postgres behavior:
    22 ```
     24
     25{{{
    2326        migrations.RemoveField(
    2427            model_name=“m”,
     
    3033            field=models.IntegerField(default=6),
    3134        ),
    32 ```
     35}}}
     36
    3337
    3438This migration runs just fine. I can even modify the field of `M` again and run a further migration. However, using `\d+` reveals that the `uniq_ab_1` constraint` is gone from the database.
Back to Top