Code

Opened 2 years ago

Closed 2 years ago

#17745 closed New feature (wontfix)

Support for PostgreSQL Arrays

Reported by: dbrgn 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

Attachments (0)

Change History (2)

comment:1 Changed 2 years ago by aaugustin

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Triage Stage changed from Unreviewed to Design 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 2 years ago by carljm

  • Resolution set to wontfix
  • Status changed from new to closed

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

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.