Changes between Initial Version and Version 1 of Ticket #23405, comment 4
- Timestamp:
- Sep 3, 2014, 10:04:58 AM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #23405, comment 4
initial v1 4 4 > I think Django should continue to prompt the user instead of guessing like South did. 5 5 6 This happens even for new fields being added. I would argue that any existing field change is a data migration anyway, and requires manual intervention.6 You're talking about having one default for new records, and another for existing records. That's clearly a data migration. 7 7 8 8 In any case, my complaint pertains to new fields being introduced, and in which case `default=''` is alread assumed by Django in any other aspect. So why not in this aspect as well?