#23834: ArrayField default is an empty string and not None
-------------------------------------+-------------------------------------
     Reporter:  ddaan                |                    Owner:  Marc
         Type:  Bug                  |  Tamlyn <marc.tamlyn@…>
    Component:  contrib.postgres     |                   Status:  closed
     Severity:  Normal               |                  Version:  master
     Keywords:                       |               Resolution:  fixed
    Has patch:  0                    |             Triage Stage:  Accepted
  Needs tests:  0                    |      Needs documentation:  0
Easy pickings:  0                    |  Patch needs improvement:  0
                                     |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by Marc Tamlyn <marc.tamlyn@…>):

 * status:  new => closed
 * owner:   => Marc Tamlyn <marc.tamlyn@…>
 * resolution:   => fixed


Comment:

 In [changeset:"9a5a4361c577d14cad303019f14ebc6d1ec01674"]:
 {{{
 #!CommitTicketReference repository=""
 revision="9a5a4361c577d14cad303019f14ebc6d1ec01674"
 Merge pull request #3531 from ddaan/ticket_23834

 fixed #23834 -- added test and fix to check for default null on ArrayField
 }}}

--
Ticket URL: <https://code.djangoproject.com/ticket/23834#comment:5>
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 post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.d2e8ba5face7e39a77052df627030134%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to