Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#29889 closed Bug (duplicate)

ArrayField cannot contain JSONField; causes SQL error

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 Miron Kizesov)

#28291 is not fixed in Django 2.1.2.

Change History (8)

comment:1 by Carlton Gibson, 6 years ago

Resolution: needsinfo
Status: newclosed

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.

Last edited 6 years ago by Carlton Gibson (previous) (diff)

in reply to:  1 comment:2 by Miron Kizesov, 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 Carlton Gibson, 6 years ago

Resolution: needsinfo
Status: closednew

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.

Version 0, edited 6 years ago by Carlton Gibson (next)

comment:4 by Tim Graham, 6 years ago

Resolution: duplicate
Status: newclosed

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 Tim Graham, 6 years ago

Description: modified (diff)

in reply to:  4 comment:6 by Miron Kizesov, 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?

comment:7 by Miron Kizesov, 6 years ago

Description: modified (diff)

comment:8 by Tim Graham, 6 years ago

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.

Note: See TracTickets for help on using tickets.
Back to Top