#27955: JSONField.default not applied in admin
----------------------------------+--------------------------------------
     Reporter:  Jannis            |                    Owner:  nobody
         Type:  Bug               |                   Status:  closed
    Component:  contrib.admin     |                  Version:  1.10
     Severity:  Normal            |               Resolution:  invalid
     Keywords:  JSONField, admin  |             Triage Stage:  Unreviewed
    Has patch:  0                 |      Needs documentation:  0
  Needs tests:  0                 |  Patch needs improvement:  0
Easy pickings:  0                 |                    UI/UX:  0
----------------------------------+--------------------------------------
Changes (by Tim Graham):

 * status:  new => closed
 * resolution:   => invalid


Old description:

> Consider a model like this:
>
> {{{
> class Example(models.Model):
>     json = JSONField(
>         default=list,
>         blank=True
>     )
> }}}
>
> Creating an object programmatically works and applies the default value
> just fine. Saving an object with an empty value for the `JSONField`
> triggers an IntegrityError because Django tries to save an object with
> `null` instead of the default.
>
> I'm not sure whether this ticket is a duplicate of
> https://code.djangoproject.com/ticket/27697 but I think this issue with
> the ignored default may have a different origin.

New description:

 Consider a model like this:

 {{{
 class Example(models.Model):
     json = JSONField(
         default=list,
         blank=True
     )
 }}}

 Creating an object programmatically works and applies the default value
 just fine. Saving an object with an empty value for the `JSONField`
 triggers an `IntegrityError` because Django tries to save an object with
 `null` instead of the default.

 I'm not sure whether this ticket is a duplicate of #27697 but I think this
 issue with the ignored default may have a different origin.

--

Comment:

 Yes, I think this is a duplicate of #27697, although the desired behavior
 you describe isn't how Django uses model field defaults. Those defaults
 are only used to populate the initial the form. If a user removes that
 value, the default isn't called again when the form is submitted.

--
Ticket URL: <https://code.djangoproject.com/ticket/27955#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/062.958b42515a7bd49ecd7c441771b2a6bf%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to