#29889 closed Bug (duplicate)
ArrayField cannot contain JSONField; causes SQL error — at Version 6
| Reported by: | Miron Kizesov | Owned by: | |
|---|---|---|---|
| Component: | contrib.postgres | Version: | 2.1 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description (last modified by )
Seems like https://code.djangoproject.com/ticket/28291 bug still not fixed in Django 2.1.2
Change History (6)
follow-up: 2 comment:1 by , 6 years ago
| Resolution: | → needsinfo |
|---|---|
| Status: | new → closed |
comment:2 by , 6 years ago
Replying to Carlton Gibson:
There’s an explicit test for the issue in #28291.
Thus you need to provide more information here: something like a failing test case, or other reprodcue for the issue you’re seeing.
I'm trying to say that this explicit test is not presented in Django 2.1.2 code https://github.com/django/django/blob/2.1.2/tests/postgres_tests/test_array.py as long as this fix https://github.com/django/django/pull/10222
So the issue haven't fixed yet in this version (but was fixed in master three month ago).
And I think test case and bug are the same as described in this issue https://code.djangoproject.com/ticket/28291.
comment:3 by , 6 years ago
| Resolution: | needsinfo |
|---|---|
| Status: | closed → new |
Right. So you're asking for a backport. Both the linked tickets from 13ba81f20a81d30b7c1cd26414fe2e009a238c7d (#28291, #24726) are listed as Bugs, so that might be feasible.
(I guess the original tickets are the place for that request, but I'll re-open for the moment.)
follow-up: 6 comment:4 by , 6 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
It's not a regression from a previous release or a major bug in a new feature so it won't be backported. See our supported versions policy.
comment:5 by , 6 years ago
| Description: | modified (diff) |
|---|
comment:6 by , 6 years ago
| Description: | modified (diff) |
|---|
Replying to Tim Graham:
It's not a regression from a previous release or a major bug in a new feature so it won't be backported. See our supported versions policy.
Ok, thank you for clarifying.
I agree it isn't a major bug. But part of my project just doesn't work due to this issue and I don't know what to do – wait (the original bug ticket was closed 3 month ago) or use development version or rework my project code.
So will this bug be fixed in next 2.1.x patch release?
There’s an explicit test for the issue in #28291.
Thus you need to provide more information here: something like a failing test case, or other reproduce for the issue you’re seeing.