#470: Add Field.db_default for defining database defaults
-------------------------------------+-------------------------------------
     Reporter:  jws                  |                    Owner:  Lily
                                     |  Foote
         Type:  New feature          |                   Status:  closed
    Component:  Database layer       |                  Version:  dev
  (models, ORM)                      |
     Severity:  normal               |               Resolution:  fixed
     Keywords:  sql schema           |             Triage Stage:  Ready for
                                     |  checkin
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"7414704e88d73dafbcfbb85f9bc54cb6111439d3" 7414704]:
 {{{
 #!CommitTicketReference repository=""
 revision="7414704e88d73dafbcfbb85f9bc54cb6111439d3"
 Fixed #470 -- Added support for database defaults on fields.

 Special thanks to Hannes Ljungberg for finding multiple implementation
 gaps.

 Thanks also to Simon Charette, Adam Johnson, and Mariusz Felisiak for
 reviews.
 }}}

-- 
Ticket URL: <https://code.djangoproject.com/ticket/470#comment:69>
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018811192796-18cf581e-a475-453e-9a41-902bcef8dc70-000000%40eu-central-1.amazonses.com.

Reply via email to