#31862 closed New feature (invalid)
Add ArrayField for all supported databases - not only postgres
Reported by: | אורי | Owned by: | nobody |
---|---|---|---|
Component: | Database layer (models, ORM) | Version: | dev |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
JSONField
has been moved from django.contrib.postgres.fields
to django.db.models
in Django 3.1. Can you move ArrayField
too from django.contrib.postgres.fields
to django.db.models
? Is there a technical reason why ArrayField
cannot be supported by all databases?
Change History (2)
comment:1 by , 4 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
comment:2 by , 4 years ago
To you point though, it was pointed out in the discussion leading to the recent changes that ArrayField would be simple enough for a user to simulate in their own project.
Note:
See TracTickets
for help on using tickets.
ArrayField maps to Postgres arrays which aren't supported on other DBs.
Please don't use the issue tracker for general questions. A quick search of the DevelopersMailingList or the related tickets here would show the history of this topic quite easily.