#24034: ArrayField.deconstruct always overwrites path
-------------------------------------+-------------------------------------
     Reporter:  kostko               |                    Owner:  Jernej
                                     |  Kos <jernej@…>
         Type:  Bug                  |                   Status:  closed
    Component:  contrib.postgres     |                  Version:  master
     Severity:  Normal               |               Resolution:  fixed
     Keywords:                       |             Triage Stage:  Accepted
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by Jernej Kos <jernej@…>):

 * status:  new => closed
 * owner:   => Jernej Kos <jernej@…>
 * resolution:   => fixed


Comment:

 In [changeset:"7c50e7eeccd4b4581542547f5ddb603bbd62a725"]:
 {{{
 #!CommitTicketReference repository=""
 revision="7c50e7eeccd4b4581542547f5ddb603bbd62a725"
 Fixed #24034 -- Don't always overwrite deconstruct path.

 Made deconstruct path overwriting for ArrayField conditional,
 so it only occurs when the deconstructed field is an instance
 of ArrayField itself and not a subclass.
 }}}

--
Ticket URL: <https://code.djangoproject.com/ticket/24034#comment:2>
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/064.90627ecf5ee58a69bf83aff63f434729%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to