Opened 5 years ago

Closed 5 years ago

Last modified 2 years ago

#17745 closed New feature (fixed)

Support for PostgreSQL Arrays

Reported by: Danilo Bargen Owned by: nobody
Component: Database layer (models, ORM) Version:
Severity: Normal Keywords:
Cc: Triage Stage: Design decision needed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Change History (4)

comment:1 Changed 5 years ago by Aymeric Augustin

Needs documentation: unset
Needs tests: unset
Patch needs improvement: unset
Triage Stage: UnreviewedDesign decision needed

As far as I can tell, django-dbarray provides a correct implementation, using the hooks currently available in the ORM.

The ORM is primarily intended to support field types used in web applications; I don't know what kind of field would best map to a PostgreSQL array.

A Google search for "django postgresql array" turns up the solution, so there's not much to gain in terms of discoverability.

For these reasons, I think this can very well live outside of core. Marking DDN so as to get a second opinion.

comment:2 Changed 5 years ago by Carl Meyer

Resolution: wontfix
Status: newclosed

I agree that features that only one of the supported database backends support are better supported by external apps when possible.

comment:3 Changed 2 years ago by Danilo Bargen

Fortunately support for Postgres arrays has been added in So the status could be changed from "wontfix" to "fixed", as a reference for people looking for this feature via Google.

comment:4 Changed 2 years ago by Aymeric Augustin

Resolution: wontfixfixed
Note: See TracTickets for help on using tickets.
Back to Top