Task #5465
Remove custom JSONField implementation, use the Postgres one instead
Start date:
Due date:
% Done:
100%
Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 59
Quarter:
Description
We've currently got a custom implementation of JSONField (backed by a TextField) that we use in a couple of places:
https://github.com/pulp/pulpcore/search?q=jsonfield&unscoped_q=jsonfield
It's also exposed via the plugin API.
Since there is no longer a need to support MariaDB and it was the main reason TextField is used for JSON content,
let's convert all the TextFields which store JSON content into Django JSONFields.
Associated revisions
History
#1
Updated by dalley over 1 year ago
- Status changed from NEW to POST
#2
Updated by dalley over 1 year ago
- Assignee set to dalley
#3
Updated by bmbouter over 1 year ago
- Sprint set to Sprint 59
With the 3.0 milestone on this issue and being at POST I think it should be on the sprint.
#4
Updated by dalley over 1 year ago
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset pulpcore|094621476d26a2789980c6d70335d466c426772f.
#5
Updated by bmbouter about 1 year ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Please register to edit this issue
.
Remove custom JSONField
Remove our TextField-based JSONField implementation and use the PostgreSQL Django-supplied one instead.
closes: #5465 https://pulp.plan.io/issues/5465