Project

Profile

Help

Task #5215

closed

Use JSONField instead of TextField for data stored in JSON format

Added by ttereshc over 3 years ago. Updated over 2 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Sprint/Milestone:
-
Start date:
Due date:
% Done:

100%

Estimated time:
Platform Release:
Groomed:
Yes
Sprint Candidate:
No
Tags:
Sprint:
Sprint 60
Quarter:

Description

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.


Related issues

Has duplicate RPM Support - Task #5326: Switch to JSONField over TextFieldCLOSED - DUPLICATE

Actions
Actions #1

Updated by dalley about 3 years ago

  • Has duplicate Task #5326: Switch to JSONField over TextField added
Actions #2

Updated by daviddavis about 3 years ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to fao89
  • Groomed changed from No to Yes
  • Sprint set to Sprint 59
Actions #3

Updated by fao89 about 3 years ago

  • Status changed from ASSIGNED to POST
Actions #4

Updated by rchan about 3 years ago

  • Sprint changed from Sprint 59 to Sprint 60
Actions #5

Updated by ttereshc about 3 years ago

  • Tags Pulp 3 RPM blocker added

Added by Fabricio Aguiar about 3 years ago

Revision 0cb7da92

converts TextFields into Django JSONFields

closes #5215 https://pulp.plan.io/issues/5215

Actions #6

Updated by Anonymous about 3 years ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100
Actions #7

Updated by ttereshc almost 3 years ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions #8

Updated by bmbouter over 2 years ago

  • Tags deleted (Pulp 3 RPM blocker)

Also available in: Atom PDF