[Django] #29889: ArrayField cannot contain JSONField; causes SQL error
Django
--------------------------------------------+------------------------
Reporter: Miron Kizesov | Owner: (none)
Type: Bug | Status: new
Component: contrib.postgres | Version: 2.1
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
--------------------------------------------+------------------------
Seems like https://code.djangoproject.com/ticket/28291 bug still not fixed
in Django 2.1.2
--
Ticket URL: <https://code.djangoproject.com/ticket/29889>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
Reporter: Miron Kizesov | Owner: (none)
Component: contrib.postgres | Version: 2.1
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Changes (by Carlton Gibson):
* status: new => closed
* resolution: => needsinfo
Comment:
There’s an
[https://github.com/vinayinvicible/django/blob/2e06ff8e141d347b6b2991891bbac01fba0396d0/tests/postgres_tests/test_array.py#L100
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.
--
Ticket URL: <https://code.djangoproject.com/ticket/29889#comment:1>
Django
Reporter: Miron Kizesov | Owner: (none)
Component: contrib.postgres | Version: 2.1
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Comment (by Miron Kizesov):
Replying to [comment:1 Carlton Gibson]:
> There’s an
[https://github.com/vinayinvicible/django/blob/2e06ff8e141d347b6b2991891bbac01fba0396d0/tests/postgres_tests/test_array.py#L100
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.
--
Ticket URL: <https://code.djangoproject.com/ticket/29889#comment:2>
Django
Reporter: Miron Kizesov | Owner: (none)
Type: Bug | Status: new
Component: contrib.postgres | Version: 2.1
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Changes (by Carlton Gibson):
* status: closed => new
* resolution: needsinfo =>
Comment:
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.
--
Ticket URL: <https://code.djangoproject.com/ticket/29889#comment:3>
Django
Reporter: Miron Kizesov | Owner: (none)
Component: contrib.postgres | Version: 2.1
Severity: Normal | Resolution: duplicate
Keywords: | 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: => duplicate
Comment:
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
[https://docs.djangoproject.com/en/dev/internals/release-process
/#supported-versions supported versions policy].
--
Ticket URL: <https://code.djangoproject.com/ticket/29889#comment:4>
Django
Reporter: Miron Kizesov | Owner: (none)
Component: contrib.postgres | Version: 2.1
Severity: Normal | Resolution: duplicate
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Description changed by Tim Graham:
Old description:
> Seems like https://code.djangoproject.com/ticket/28291 bug still not
> fixed in Django 2.1.2
New description:
#28291 is not fixed in Django 2.1.2.
--
--
Ticket URL: <https://code.djangoproject.com/ticket/29889#comment:5>
Django
Reporter: Miron Kizesov | Owner: (none)
Component: contrib.postgres | Version: 2.1
Severity: Normal | Resolution: duplicate
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Old description:
> #28291 is not fixed in Django 2.1.2.
New description:
Seems like https://code.djangoproject.com/ticket/28291 bug still not fixed
in Django 2.1.2
--
Comment (by Miron Kizesov):
Replying to [comment:4 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
[https://docs.djangoproject.com/en/dev/internals/release-process
/#supported-versions 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?
--
Ticket URL: <https://code.djangoproject.com/ticket/29889#comment:6>
Django
Reporter: Miron Kizesov | Owner: (none)
Component: contrib.postgres | Version: 2.1
Severity: Normal | Resolution: duplicate
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Description changed by Miron Kizesov:
Old description:
> Seems like https://code.djangoproject.com/ticket/28291 bug still not
> fixed in Django 2.1.2
New description:
#28291 is not fixed in Django 2.1.2.
--
--
Ticket URL: <https://code.djangoproject.com/ticket/29889#comment:7>
Django
Reporter: Miron Kizesov | Owner: (none)
Component: contrib.postgres | Version: 2.1
Severity: Normal | Resolution: duplicate
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Comment (by Tim Graham):
The fix will be released in Django 2.2. It won't be backported to the
2.1.x branch. It looks like you could monkeypatch `ArrayField` to add the
missing method.
--
Ticket URL: <https://code.djangoproject.com/ticket/29889#comment:8>