Issue #3217
closed
PythonPackageContent and PythonImporter should not use ArrayField
Description
While ArrayField is nice and simple for modeling it is postgresql only. We should not lock down on the db to one technology.
- 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)
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
- Triaged changed from No to Yes
- Status changed from NEW to ASSIGNED
- Status changed from ASSIGNED to POST
- Status changed from POST to MODIFIED
- Platform Release set to 3.0.0
Also available in: Atom
PDF
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