#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 |
Description
It would be nice if Django would natively support PostgreSQL's Array Types.
See also:
- http://stackoverflow.com/questions/4400762/how-to-map-postgresql-array-field-in-django-orm
- http://stackoverflow.com/questions/4213332/how-does-django-model-after-text-in-postgresql
Existing possible solutions:
Change History (4)
comment:1 by , 13 years ago
Triage Stage: | Unreviewed → Design decision needed |
---|
comment:2 by , 13 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
I agree that features that only one of the supported database backends support are better supported by external apps when possible.
comment:3 by , 10 years ago
Fortunately support for Postgres arrays has been added in https://github.com/django/django/pull/2485. So the status could be changed from "wontfix" to "fixed", as a reference for people looking for this feature via Google.
comment:4 by , 10 years ago
Resolution: | wontfix → fixed |
---|
Note:
See TracTickets
for help on using tickets.
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.