Ticket #459 (closed defect: fixed)

Opened 5 years ago

Last modified 4 years ago

No migration is needed for changes to blank= on a model field

Reported by: noah@… Owned by: andrew
Priority: minor Milestone: 0.7.2
Component: migrations Version: 0.7
Keywords: Cc:

Description

An example from an autogenerated migration:

class Migration(SchemaMigration):
    
    def forwards(self, orm):
        
        # Changing field 'Consumer.key'
        db.alter_column('oauth_consumer', 'key', self.gf('django.db.models.fields.CharField')(max_length=256, blank=True))
    
    
    def backwards(self, orm):

        # Changing field 'Consumer.key'
        db.alter_column('oauth_consumer', 'key', self.gf('django.db.models.fields.CharField')(max_length=256))

No migration in needed since blank doesn't actually change the DB.

Change History

comment:1 Changed 5 years ago by andrew

  • Status changed from new to assigned
  • Milestone set to 0.7.2

comment:2 Changed 4 years ago by andrew

  • Status changed from assigned to closed
  • Resolution set to fixed

Fixed in [c9d6e2058ec6].

Note: See TracTickets for help on using tickets.