Investigate using postgresql ArrayField rather than JSONField for simple, one-dimensional lists of strings

Open
#364 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
django, postgresql, python
Domain
databases

Research direction

Start with pulp_python/app/models.py lines 113-117 and the Django ArrayField documentation. Compare ArrayField with JSONField for the simple one-dimensional string lists described there, including efficiency and convenience. Done means producing a clear recommendation about whether this approach is suitable for adoption by other plugins.

Written by the indexing model from the issue text.

Description

We've got a ton of these: https://github.com/pulp/pulp_python/blob/master/pulp_python/app/models.py#L113-L117

It would be interesting whether ArrayField is more efficient or convenient for this use case. https://docs.djangoproject.com/en/3.2/ref/contrib/postgres/fields/#arrayfield

We should do some research to see if it's a good idea - other plugins may want to adopt it also.

Dominant language
Python
Stars
49
Forks
88
Avg merge
1d 10h
Merged PRs (30d)
31

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from pulp/pulp_python

All issues in pulp/pulp_python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.