Project

Profile

Help

Issue #3217

PythonPackageContent and PythonImporter should not use ArrayField

Added by bizhang almost 4 years ago. Updated 11 months ago.

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.

Associated revisions

Revision b8464a43 View on GitHub
Added by werwty almost 4 years ago

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

History

#1 Updated by bizhang almost 4 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)

#2 Updated by bizhang almost 4 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

#3 Updated by bizhang almost 4 years ago

  • Triaged changed from No to Yes

#4 Updated by bizhang almost 4 years ago

  • Status changed from NEW to ASSIGNED

#5 Updated by bizhang almost 4 years ago

  • Status changed from ASSIGNED to POST

#6 Updated by werwty almost 4 years ago

  • Status changed from POST to MODIFIED

#7 Updated by bmbouter over 2 years ago

  • Tags deleted (Pulp 3)

#8 Updated by dalley 11 months ago

  • Platform Release set to 3.0.0

Also available in: Atom PDF