Actions
Issue #3217
closedPythonPackageContent and PythonImporter should not use ArrayField
Status:
MODIFIED
Priority:
Normal
Assignee:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version - Python:
Platform Release:
3.0.0
Target Release - Python:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:
Description
While ArrayField is nice and simple for modeling it is postgresql only. We should not lock down on the db to one technology.
Updated by bizhang about 6 years ago
- Project changed from Pulp to Python Support
- Subject changed from Error on updating ArrayField in Pulp3 to PythonPackageContent and PythonImporter should not use ArrayField
- Description updated (diff)
Updated by bizhang about 6 years ago
After talking to daviddavis it seems that we have 2 opinions:
1.) one to many Join table
I think this is the most 'correct' relational db solution. It is, however, a very overkill way to store what is essentially a list of strings.
2.) 'stringified' JSON object
This would require that we parse the stringified json object on create/read/update. We will possibly have to override the update endpoint on the viewset
Updated by bizhang about 6 years ago
- Status changed from ASSIGNED to POST
Added by werwty about 6 years ago
Updated by werwty about 6 years ago
- Status changed from POST to MODIFIED
Applied in changeset b8464a43b7f3299bd2dc780c0d102709b791137d.
Actions
Update models to use TextField in lieu of ArrayField
fixes #3217 https://pulp.plan.io/issues/3217
fixes #1132 https://pulp.plan.io/issues/1132