#23043: Fix or document inconsistent handling of field defaults by migrations
---------------------------------+------------------------------------
     Reporter:  timo             |                    Owner:  nobody
         Type:  Bug              |                   Status:  new
    Component:  Migrations       |                  Version:  1.7-rc-1
     Severity:  Release blocker  |               Resolution:
     Keywords:                   |             Triage Stage:  Accepted
    Has patch:  0                |      Needs documentation:  0
  Needs tests:  0                |  Patch needs improvement:  0
Easy pickings:  0                |                    UI/UX:  0
---------------------------------+------------------------------------
Changes (by shai):

 * cc: andrewgodwin, shai (added)
 * type:  Cleanup/optimization => Bug
 * severity:  Normal => Release blocker
 * stage:  Unreviewed => Accepted


Comment:

 I think this is a bug, not a cleanup/optimization, and a release blocker
 at that.

 South had added defaults in the database until version 0.7.4; I think it
 took another release or two to get rid of them completely. The realization
 that defaults should never be left in the database (they should only be
 used when adding new columns to existing tables, and then removed) was
 christened in pain and angst -- some related to callable, as @timo noted;
 another ill-effect, unique to Oracle, was that the presence of default
 date-time values required special, non-trivial handling for schema backup
 and restore (ask me if you want details; irrelevant here).

 Defaults in a Django-managed database are evil. Kill them with fire.

 (the change in type and severity is tentative, feel free to revert if you
 have can convince yourself otherwise)

-- 
Ticket URL: <https://code.djangoproject.com/ticket/23043#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.b029e7cc45e2747289ad2cd156c59cc5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to