Project

Profile

Help

Actions
Send by e-mail Copy link

Task #5465

closed

Remove custom JSONField implementation, use the Postgres one instead

Added by dalley over 5 years ago. Updated about 5 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
dalley
Category:
-
Sprint/Milestone:
3.0.0
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.

Actions
Copy link
 #2

Updated by dalley over 5 years ago

  • Assignee set to dalley
Actions
Copy link
 #3

Updated by bmbouter over 5 years 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.

Added by dalley over 5 years ago

Revision 09462147 | View on GitHub

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

Actions
Copy link
 #4

Updated by dalley over 5 years ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100
Actions
Copy link
 #5

Updated by bmbouter about 5 years ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
Send by e-mail Copy link

Also available in: Atom PDF