Ticket #463 (closed enhancement: fixed)

Opened 6 years ago

Last modified 5 years ago

CharField set to blank still requires default value

Reported by: btaylordesign@… Owned by: andrew
Priority: major Milestone: 0.7.2
Component: commands Version: 0.7
Keywords: Cc:


To the best of my knowledge, it is not advisable to use null=True on CharFields?, but better use use an empty string.

When attempting to create a schemamigration on a CharField? specified as blank=True, South prompts me to either alter my model, or enter a one-time value for the field.

It seems as though South should treat blank=True the same as default= for CharFields?. I can't recall a single instance where I've ever specified default= on a CharField? in over two years of developing with Django.

Kind regards,
Brandon Taylor

Change History

comment:1 Changed 6 years ago by andrew

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

comment:2 Changed 5 years ago by andrew

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

Fixed in [ec28c7754e51].

Note: See TracTickets for help on using tickets.