#35454: ArrayField with default throwing a ValidationError on full_clean
-------------------------------------+-------------------------------------
Reporter: hfroot | Owner: nobody
Type: Uncategorized | Status: closed
Component: Database layer | Version: 5.0
(models, ORM) |
Severity: Normal | Resolution: invalid
Keywords: full_clean, | Triage Stage:
ArrayField, ValidationError | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Jacob Walls):
* resolution: => invalid
* status: new => closed
Comment:
The docs on the additional fields from `django.contrib.postgres.fields` I
think (rightly) assume more basic knowledge about `null`, `blank`, and
`default`, so I'm reluctant to suggest we re-document those basics on
`ArrayField`.
> I fixed the issue by adding blank=True to the ArrayField definition.
Glad you found the answer.
--
Ticket URL: <https://code.djangoproject.com/ticket/35454#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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018f796fa28d-3644afb1-001a-44b9-8002-21dfc5a412dd-000000%40eu-central-1.amazonses.com.
